How to Get Logs
For version 3 we have improved the debug abilities of our software. For those who are interested this topic will describe how to activate the special debug mode and how to understand whats happening in detail.
This is the general overview. You can see the general statistics and health on this view.
The chart is showing 2 very important lines. The first is the heartbeat, on the background within the software we have setup an separate thread which is counting the seconds which has passed. This is called an heartbeat because we are expecting to count 20 seconds each time we update the chart. If the chart shows less heartbeats then something is up. Its an telltale of an CPU which can not handle the load the software requires.
The second line is showing Waiting Threads. This is an technical name, but its telling how much threads are waiting to be executed. In theory if your computer has less cores this stack of waiting threads becomes pretty big. Again this is an sign the computer can not handle the load. But keep in mind having thread waiting is very normal too, this software is simply very heavily multi-threaded.
Inside the totals there are a few fields of interest, first of all we can see if any exception have happened inside the software while it was running. Secondly the database field can tell if the database if functioning properly. For the software its essential to have an good quick functioning database.
The history engine is showing the status of the price history and the price history synchronization proces.
The chart are showing 2 lines representing an stack, which can be compared to an todo list. Again both lines are very important and in this case they are designed to "take-over". The WorkingStack is the initial todo list ofall the price markets which required to be synced. Once the WorkingStack is done with an price market its passed to the AlignmentStack. In here the prices are keeped up to date.
The WorkingStack is designed to reach 0. So over time this stack has to become empty and then everything is nicely in sync. It might take an while before it reaches the 0 because only of the full price history is perfectly aligned inside the database then is removed from the WorkingStack.
In the event where is never reaches 0 its an telltale of an problem. It means no price updates are received from both the price driver and the white server. So its impossible to those the prices aligned nicely. To see which price market are affected you can expand the details listed below it. The details will tell how many times an sync is called, if the price market has been given up to be synced and such.
Its just the technical name, but at the white server we can see how the price backbone is preforming. This is the backup system to get price update in case you have connections problems. Its also used as main source when the low-power mode is activated.
On the chart you can see 2 lines, one showing the amount of subscriptions (price requests) to the White Server and the other line shows the ServerMessages received back. These (of course) represent price updates.
To detect issues you need to watch the subscriptions. In general its only needed to subscribe once to our server. But if more subscriptions happen then its an telltale of missing price data. If you see this its best to give us an sign so we can resolve this. There are additional details available for which price markets are involved. To see it you need to expand the details shown below.
The software is designed to switch over automatically in the event an price server gets compromised somehow. We list this number as server re-selections, and if this number goes up very high then its an telltale of an firewall blocking or an very big problem on our end.
The price driver is the overall driver to handle the price updates. It shows an chart telling how many updates have been progressed for the last 20 seconds.
Except for seeing the load the updates are doing you can not really see much directly at this view. However, if you expand the details then an nice table will show up. It will tell per price source how many errors/re-connections have been done in total. These are the most important numbers because its telling how stable the price driver itself is. Next the amount of updates are listed (collected per minute) to see if some data is missing. On the most right corner there is the average required time listed for the connection. The is the second most important number, if it list an very high time needed then it means your connection to this exchange is not good.
The account driver is the overall driver to handle all the accounts. Also here the charts is showing the amount of updates from all the activated accounts. (including the simulated ones)
The account debug view will become available inside version 3.0.11.
Submitting your Logs on the Forum
To submit the logs on the Forum, you will want to copy the relevant part of the debug logs and then head over to the Support Forums and create a post about the issue. When copying the logs, please use the [code][/code] tags and paste the logs inside of the Code Tags.
For instance: [code] PASTE LOGS HERE [/code]
Be sure to be descriptive of the issue you are experiencing so that the Haasbot developers can look into the issue and provide fixes as soon as they can.