XLCubed is now FluenceXL. The new wiki can be found here: https://help.fluencexl.com/ |
Difference between revisions of "Logging"
(Edited the sample configs to make it more relevant for the default cases) |
|||
Line 30: | Line 30: | ||
} | } | ||
− | + | Alternatively, you can log to the debug output, which you can capture using [https://learn.microsoft.com/en-us/sysinternals/downloads/debugview DebugView] a free tool from Microsoft. Note that this will have information from other programs running on the computer, so may be harder to interpret. | |
{ | { |
Revision as of 14:16, 18 April 2023
From XLCubed v10.0.150 it has become possible to capture logs from XLCubed activity.
The logs for Excel and Web are configured using a JSON file called appsettings.json.
- For the web this is deployed by default in the /XLCubedWeb directory and will log to a file in the Logs sub-directory.
- For Excel this file should be created in the %appdata%\XLCubed Ltd\XLCubed Excel Edition folder (you can type this address into File Explorer to go to the correct folder)
The log configuration can have different output targets which you can configure as shown below. You will have to restart Excel if you change the configuration.
Sample configurations
This will log Verbose messages to the debug window and to a file. Note that backslashes in the file path must be doubled.
{ "Serilog": { "MinimumLevel": "Verbose", "WriteTo": [ { "Name": "Debug" } , { "Name": "File", "Args": { "path": "C:\\Path\\To\\Logs\\error.log", "rollingInterval": "Day", "retainedFileCountLimit": 10, "restrictedToMinimumLevel": "Verbose" } } ] } }
Alternatively, you can log to the debug output, which you can capture using DebugView a free tool from Microsoft. Note that this will have information from other programs running on the computer, so may be harder to interpret.
{ "Serilog": { "MinimumLevel": "Debug", "WriteTo": [ { "Name": "Debug" } ] } }