document new log-fetcher

source/user_guide/helm_settings.rst

@@ -89,7 +89,7 @@ In the following example, we used the application, reloaded the page and
 re used it. In an actual use case, you should use it more than twice in 
 order to have an acurate estimation of the memory consumption.
 
-.. code-block:: txt
+.. code-block:: text
 
     fca3d08757e1   rshiny-k8s-example-r_shiny-server_1   0.00%     35.47MiB / 31.09GiB   ...
     fca3d08757e1   rshiny-k8s-example-r_shiny-server_1   17.30%    430.63MiB / 31.09GiB   ...
@@ -557,7 +557,7 @@ clic on the text ``log-fetcher-in-dev`` (2 in the image).
             :alt: Find task log-fetcher
 
 You can then either directly clic on Run job, you will see the last lines 
-(200 by default as of juky 2023).
+(200 by default as of july 2023).
 You can also specify a custom amount of line, to do so specify the value
 of the variable ``LAST_ROWS_COUNT``. If you want all logs since startup
 set the value to ``-1``.
@@ -572,7 +572,7 @@ Which produce the following:
   :align: center
   :alt: Reading output of log-fetcher
 
-The logs will be at the bottom of the page (3 in the image).
+The logs will be at the bottom of the page (1 in the image).
 Here we see that the Shiny server has started well.
 
 The quota will be at the beginning of the logs (2 in the image).
@@ -589,6 +589,9 @@ Quota should be read as:
     | Ram  | 512Mi    | 1Gi    | 5Gi   |
     +------+----------+--------+-------+
 
+The logs can also be downloaded, the file(s) can be found in the 
+"Job artifacts" section (3 in the image).
+
 If you want to restart the task with a different number of rows, first you 
 have to delete the log with the trash button at the top right of the page 
-(1 in the image).
+(4 in the image).