This tutorial details procedures to follow when you run into difficulties when developing with Finsemble.
The Central Logger is an incredibly useful tool for diagnosing Finsemble problems and will be your first line of defense. Its tutorial details how you can set log levels and change logging details.
Central Loggeris running, then click on its entry to bring up its window.
showConsole(). This should bring up the Central Logger.
Finsemble runs on top of a Chromium container. Chromium contains the same debugging tools that you are used to in Chrome. Press CTRL+SHIFT+I to pop up Chromium's debug tools in a new window.
An alternative debugging method is to open a browser and navigate to http://localhost:9090. Each window in your application is listed on that page. Click on the window you wish to debug and a Chromium debugger will be launched for that window. There are some limitations (e.g., you can't evaluate code in the console in a remote session), but it largely acts as you would expect.
We're available to provide support. To capture log data for field support, follow these steps.
Launch the Central Logger.
Click the "Finsemble Support" button. This toggles the settings to capture a broad range of log levels.
Click "Clear Data" to start fresh.
Try to recreate the problem that you were experiencing. If gathering logs for a start-up problem, restart Finsemble to see if the error occurs.
If the problem occurred, save the log by clicking "Export Log."
Most log files are large. Zip the log files to compress them before sending them to ChartIQ.
Email the log file to firstname.lastname@example.org. Please include a detailed description of the problem you're experiencing in your email so that we can properly diagnose the problem.
Important: This detailed logging level might introduce performance issues to your Finsemble application. Once debugging is completed, it's best reduce the logging levels to their default state. To reset the log settings back to their original values, click the "Default" button under Quick Views.
For more information about diagnosing issues so you can iterate quickly, check out Debugging Finsemble.