Logging is a very useful feature that allows to see what exactly the software is doing or has been doing at any given point in time.
It helps to learn the software and is invaluable for troubleshooting.
When the software is single-threaded (i.e. does only one thing at a time), it is sufficient to keep just one log. However, when many tasks are run at once, one log would be a big mess. Therefore, we had to introduce a concept of Context logging
Context logging means that each particular task in the software gets its own log, so you can be sure that there is no mix of actions from different tasks. It is much easier to read and understand. Furthermore, context logging is also applied to some items in the software, like accounts, proxies, etc. For example, when a proxy is being validated, the information about it is sent to 2 context logs - the one for that particular validation task, and the other one - for the proxy. So if you ever wanted to know when a particular proxy was validated, how many times and what were the results in each particular case - you just need to open that proxy's context log.
Context logs are usually accessible from within the software when you click on an item that supports context logging. For proxies, that would be under the IP rotation->Proxies tab. When you select a proxy of interest, click on the "Logs" tab to the right and you will see that proxy's context log.
Records in the Context logs may be of 4 different types:
- Error messages
- Warning messages
- Information messages
- Debug messages
By default, messages of the first three types are visible, and debug messages are hidden. If you would like to see more details - just click on the Show debug messages button