mirror of
https://github.com/freqtrade/freqtrade.git
synced 2026-02-13 09:40:29 +00:00
Deployed 33c8969 to develop in en with MkDocs 1.6.1 and mike 2.1.3
This commit is contained in:
@@ -2116,11 +2116,12 @@ as the watchdog.</p>
|
||||
</div>
|
||||
<h2 id="advanced-logging">Advanced Logging<a class="headerlink" href="#advanced-logging" title="Permanent link">¶</a></h2>
|
||||
<p>Freqtrade uses the default logging module provided by python.
|
||||
Python allows for extensive <a href="https://docs.python.org/3/library/logging.config.html#logging.config.dictConfig">logging configuration</a> in this regards - way more than what can be covered here.</p>
|
||||
<p>Default logging (Colored terminal output) is setup by default if no <code>log_config</code> is provided.
|
||||
Using <code>--logfile logfile.log</code> will enable the RotatingFileHandler.
|
||||
If you're not content with the log format - or with the default settings provided for the RotatingFileHandler, you can customize logging to your liking.</p>
|
||||
<p>The default configuration looks roughly like the below - with the file handler being provided - but not enabled.</p>
|
||||
Python allows for extensive <a href="https://docs.python.org/3/library/logging.config.html#logging.config.dictConfig">logging configuration</a> in this regard - way more than what can be covered here.</p>
|
||||
<p>Default logging format (coloured terminal output) is set up by default if no <code>log_config</code> is provided in your freqtrade configuration.
|
||||
Using <code>--logfile logfile.log</code> will enable the RotatingFileHandler.</p>
|
||||
<p>If you're not content with the log format, or with the default settings provided for the RotatingFileHandler, you can customize logging to your liking by adding the <code>log_config</code> configuration to your freqtrade configuration file(s).</p>
|
||||
<p>The default configuration looks roughly like the below, with the file handler being provided but not enabled as the <code>filename</code> is commented out.
|
||||
Uncomment this line and supply a valid path/filename to enable it.</p>
|
||||
<div class="highlight"><pre><span></span><code><span class="p">{</span>
|
||||
<span class="w"> </span><span class="nt">"log_config"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span>
|
||||
<span class="w"> </span><span class="nt">"version"</span><span class="p">:</span><span class="w"> </span><span class="mi">1</span><span class="p">,</span>
|
||||
@@ -2160,12 +2161,12 @@ If you're not content with the log format - or with the default settings provide
|
||||
<p>Highlighted lines in the above code-block define the Rich handler and belong together.
|
||||
The formatter "standard" and "file" will belong to the FileHandler.</p>
|
||||
</div>
|
||||
<p>Each handler must use one of the defined formatters (by name) - and it's class must be available and a valid logging class.
|
||||
To actually use a handler - it must be in the "handlers" section inside the "root" segment.
|
||||
<p>Each handler must use one of the defined formatters (by name), its class must be available, and must be a valid logging class.
|
||||
To actually use a handler, it must be in the "handlers" section inside the "root" segment.
|
||||
If this section is left out, freqtrade will provide no output (in the non-configured handler, anyway).</p>
|
||||
<div class="admonition tip">
|
||||
<p class="admonition-title">Explicit log configuration</p>
|
||||
<p>We recommend to extract the logging configuration from your main configuration, and provide it to your bot via <a href="../configuration/#multiple-configuration-files">multiple configuration files</a> functionality. This will avoid unnecessary code duplication.</p>
|
||||
<p>We recommend to extract the logging configuration from your main freqtrade configuration file, and provide it to your bot via <a href="../configuration/#multiple-configuration-files">multiple configuration files</a> functionality. This will avoid unnecessary code duplication.</p>
|
||||
</div>
|
||||
<hr />
|
||||
<p>On many Linux systems the bot can be configured to send its log messages to <code>syslog</code> or <code>journald</code> system services. Logging to a remote <code>syslog</code> server is also available on Windows. The special values for the <code>--logfile</code> command line option can be used for this.</p>
|
||||
|
||||
File diff suppressed because one or more lines are too long
@@ -2085,16 +2085,19 @@ Some websites that list and rank Freqtrade strategies show impressive backtest r
|
||||
of pairs you have in your pairlist within a reasonable time. Freqtrade will warn you in the logs if there are significant data processing delays.</li>
|
||||
</ul>
|
||||
<h2 id="controlling-or-monitoring-a-running-bot">Controlling or monitoring a running bot<a class="headerlink" href="#controlling-or-monitoring-a-running-bot" title="Permanent link">¶</a></h2>
|
||||
<p>Once your bot is running in dry or live mode, Freqtrade has five mechanisms to control or monitor a running bot:</p>
|
||||
<p>Once your bot is running in dry or live mode, Freqtrade has six mechanisms to control or monitor a running bot:</p>
|
||||
<ul>
|
||||
<li><strong><a href="../freq-ui/">FreqUI</a></strong>: The easiest to get started with, FreqUI is a web interface to see and control current activity of your bot.</li>
|
||||
<li><strong><a href="../telegram-usage/">Telegram</a></strong>: On mobile devices, Telegram integration is available to get alerts about your bot activity and to control certain aspects.</li>
|
||||
<li><strong><a href="https://github.com/freqtrade/ftui">FTUI</a></strong>: FTUI is a terminal (command line) interface to Freqtrade, and allows monitoring of a running bot only.</li>
|
||||
<li><strong><a href="../rest-api/">REST API</a></strong>: The REST API allows programmers to develop their own tools to interact with a Freqtrade bot.</li>
|
||||
<li><strong><a href="../rest-api/#consuming-the-api">freqtrade-client</a></strong>: A python implementation of the REST API, making it easy to make requests and consume bot responses from your python apps or the command line.</li>
|
||||
<li><strong><a href="../rest-api/#available-endpoints">REST API endpoints</a></strong>: The REST API allows programmers to develop their own tools to interact with a Freqtrade bot.</li>
|
||||
<li><strong><a href="../webhook-config/">Webhooks</a></strong>: Freqtrade can send information to other services, e.g. discord, by webhooks.</li>
|
||||
</ul>
|
||||
<h3 id="logs">Logs<a class="headerlink" href="#logs" title="Permanent link">¶</a></h3>
|
||||
<p>Freqtrade generates extensive debugging logs to help you understand what's happening. Please familiarise yourself with the information and error messages you might see in your bot logs.</p>
|
||||
<p>Logging by default occurs on standard out (the command line). If you want to write out to a file instead, many freqtrade commands, including the <code>trade</code> command, accept the <code>--logfile</code> option to write to a file.</p>
|
||||
<p>Check the <a href="../faq/#how-do-i-search-the-bot-logs-for-something">FAQ</a> for examples.</p>
|
||||
<h2 id="final-thoughts">Final Thoughts<a class="headerlink" href="#final-thoughts" title="Permanent link">¶</a></h2>
|
||||
<p>Algo trading is difficult, and most public strategies are not good performers due to the time and effort to make a strategy work profitably in multiple scenarios.</p>
|
||||
<p>Therefore, taking public strategies and using backtests as a way to assess performance is often problematic. However, Freqtrade provides useful ways to help you make decisions and do your due diligence.</p>
|
||||
|
||||
Reference in New Issue
Block a user