Update analysis guides (#256)

* adding logs analysis

* Update discover.pdf

* Update pages/tidal tools/analyze_logs.md

Co-authored-by: Philip Rees <philrees@gmail.com>

* Update discover.pdf

---------

Co-authored-by: Philip Rees <philrees@gmail.com>

Author: ramizpolic

_data/sidebars/main_sidebar.yml

@@ -73,6 +73,9 @@ entries:
           - title: Database Analysis
             output: web
             url: analyze-database.html
+          - title: HTTP Web Log Analysis
+            output: web
+            url: analyze-logs.html
           - title: Application Interview Best Practices
             output: web
             url: interviews.html

book/discover.pdf

@@ -0,0 +1,62 @@
+---
+title: Analyze your HTTP Web Logs
+keywords: source, assessment, readiness, analyze
+last_updated: May, 2023
+summary: "Analyze HTTP web logs to see insights on an applications usage patterns over time."
+sidebar: main_sidebar
+permalink: analyze-logs.html
+folder: tidaltools
+---
+Not sure when the best time to perform a migration cut over is? 
+With Tidal, you have the option to analyze the HTTP web logs associated with your applications.
+
+The analysis will provide relevant insights regarding request volumes, users, and bandwidth usage patterns over time. 
+This information can be taken into account when planning and scheduling the optimal window for the migration.
+
+It is capable of analyzing HTTP logs generated by **Apache**, **IIS**, and **NGINX**.
+
+{% include note.html content="The analysis does not collect any data." %}
+
+## Perform the analysis
+
+Perform the HTTP log analysis and obtain a PDF report. This is Tidal Tools' default behaviour. 
+To do so, all you need to do is run the following command.
+
+```bash
+tidal analyze logs [path/to/log_file]
+   ```
+
+   Alternatively, you can pass the location or even wildcard to analyze multiple HTTP log files.
+   Non-supported files will be skipped.
+
+```bash
+tidal analyze code [/path/to/log_folder] [/path/to/other_folder]/*.log
+```
+
+## Upload log analysis
+If you would like to preserve the log analysis results, you can do so by uploading only the log analysis metadata.
+This can help track the changes and allow you to easily generate reports.
+
+You can get started by running log analysis:
+
+```bash
+tidal analyze log [directory] --json
+```
+   
+And upload the produced JSON log analysis result file by using the following command:
+   
+```bash
+tidal analyze log upload [file] --app-id [app_id_for_your_application]
+```
+
+{% include note.html content="The log analysis result data must be uploaded manually." %}
+
+## Converting JSON to PDF reports
+If your log anaysis data has been exported to JSON for reusability, or you would like to
+convert saved data into PDF, you can do so by running:
+
+```bash
+tidal analyze log generate [file]
+```
+
+This will convert a JSON result into a PDF report.

pages/tidal tools/analyze_logs.md

@@ -52,10 +52,10 @@ When analyzing a source code (or multiple), you have two options.
    tidal analyze code --app-id [app_id_for_your_application]
    ```
 
-   Alternatively, you can pass the location to the source code.
+   Alternatively, you can pass multiple locations or even wildcard for analysis. You can even specify individual files.
 
    ```bash
-   tidal analyze code [/path/to/source-code] --app-id [app_id_for_your_application]
+   tidal analyze code [/path/to/source-code-A] [/path/to/source-code-B] --app-id [app_id_for_your_application]
    ```
 
 2. Perform the source code analysis and upload the results **at a later time**. The following section will explain how to run database analysis in **offline mode**
@@ -87,10 +87,10 @@ These are the steps you need to follow in order to bypass internet access limita
    tidal analyze code --offline
    ```
 
-   Alternatively, you can pass the location to the source code.
+   Alternatively, you can pass multiple locations or even wildcard for analysis. You can even specify individual files.
 
    ```bash
-   tidal analyze code [/path/to/source-code] --offline
+   tidal analyze code [/path/to/source-code-A] [/path/to/source-code-B] --offline
    ```
 
    Note: