By default, HEAVY.AI uses logs with a symbolic link referencing the current HEAVY.AI server instance. These logs are located in the /log directory, which is
/var/lib/heavyai/storage in a standard installation. These logs are described below.
This is the best source of information for troubleshooting and the first place you should check for issues. This log will capture the following:
- Configuration settings in place when
- Queries by user and session ID, with execution time (time for the query to run) and total time (execution time plus time spent waiting to execute plus network wait time).
Reports nonfatal warning messages.
Logs non-fatal error messages, as well as errors related to data ingestion.
Reports 'check failed' messages and a line number to identify where the error occurred.
Accessing the logs
The Administrator can view the logs, accessing directly to the server with SSH, using the Log Files section of the Control Panel in Heavy Immerse, or accessing them directly using Heavy Immerse
Please look at the Control Panel and Admin Console of Heavy Immerse to further information.
Monitoring the performances of the dashboards.
Using Chrome’s Developer Tools, you can interact with data in Heavy Immerse to see the SQL generated and the relative response times from heavyDB. The syntax is
SQLlogging(true), entered under the console tab inline, as shown below.
Once SQL Logging is turned on, you can interact with the dashboard, see the SQL generated and monitor the response timing involved.
Note: When adding SQLlogging(true) or SQLlogging(false) you need to reload the page for the changes to take effect
Article is closed for comments.