Skip to content

Commit 96c5f0d

Browse files
ramizpolicprees1
andauthored
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>
1 parent d9bea3e commit 96c5f0d

File tree

4 files changed

+69
-4
lines changed

4 files changed

+69
-4
lines changed

_data/sidebars/main_sidebar.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -73,6 +73,9 @@ entries:
7373
- title: Database Analysis
7474
output: web
7575
url: analyze-database.html
76+
- title: HTTP Web Log Analysis
77+
output: web
78+
url: analyze-logs.html
7679
- title: Application Interview Best Practices
7780
output: web
7881
url: interviews.html

book/discover.pdf

182 Bytes
Binary file not shown.

pages/tidal tools/analyze_logs.md

Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
---
2+
title: Analyze your HTTP Web Logs
3+
keywords: source, assessment, readiness, analyze
4+
last_updated: May, 2023
5+
summary: "Analyze HTTP web logs to see insights on an applications usage patterns over time."
6+
sidebar: main_sidebar
7+
permalink: analyze-logs.html
8+
folder: tidaltools
9+
---
10+
Not sure when the best time to perform a migration cut over is?
11+
With Tidal, you have the option to analyze the HTTP web logs associated with your applications.
12+
13+
The analysis will provide relevant insights regarding request volumes, users, and bandwidth usage patterns over time.
14+
This information can be taken into account when planning and scheduling the optimal window for the migration.
15+
16+
It is capable of analyzing HTTP logs generated by **Apache**, **IIS**, and **NGINX**.
17+
18+
{% include note.html content="The analysis does not collect any data." %}
19+
20+
## Perform the analysis
21+
22+
Perform the HTTP log analysis and obtain a PDF report. This is Tidal Tools' default behaviour.
23+
To do so, all you need to do is run the following command.
24+
25+
```bash
26+
tidal analyze logs [path/to/log_file]
27+
```
28+
29+
Alternatively, you can pass the location or even wildcard to analyze multiple HTTP log files.
30+
Non-supported files will be skipped.
31+
32+
```bash
33+
tidal analyze code [/path/to/log_folder] [/path/to/other_folder]/*.log
34+
```
35+
36+
## Upload log analysis
37+
If you would like to preserve the log analysis results, you can do so by uploading only the log analysis metadata.
38+
This can help track the changes and allow you to easily generate reports.
39+
40+
You can get started by running log analysis:
41+
42+
```bash
43+
tidal analyze log [directory] --json
44+
```
45+
46+
And upload the produced JSON log analysis result file by using the following command:
47+
48+
```bash
49+
tidal analyze log upload [file] --app-id [app_id_for_your_application]
50+
```
51+
52+
{% include note.html content="The log analysis result data must be uploaded manually." %}
53+
54+
## Converting JSON to PDF reports
55+
If your log anaysis data has been exported to JSON for reusability, or you would like to
56+
convert saved data into PDF, you can do so by running:
57+
58+
```bash
59+
tidal analyze log generate [file]
60+
```
61+
62+
This will convert a JSON result into a PDF report.

pages/tidal tools/sourcecode.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -52,10 +52,10 @@ When analyzing a source code (or multiple), you have two options.
5252
tidal analyze code --app-id [app_id_for_your_application]
5353
```
5454

55-
Alternatively, you can pass the location to the source code.
55+
Alternatively, you can pass multiple locations or even wildcard for analysis. You can even specify individual files.
5656

5757
```bash
58-
tidal analyze code [/path/to/source-code] --app-id [app_id_for_your_application]
58+
tidal analyze code [/path/to/source-code-A] [/path/to/source-code-B] --app-id [app_id_for_your_application]
5959
```
6060

6161
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
8787
tidal analyze code --offline
8888
```
8989

90-
Alternatively, you can pass the location to the source code.
90+
Alternatively, you can pass multiple locations or even wildcard for analysis. You can even specify individual files.
9191

9292
```bash
93-
tidal analyze code [/path/to/source-code] --offline
93+
tidal analyze code [/path/to/source-code-A] [/path/to/source-code-B] --offline
9494
```
9595

9696
Note:

0 commit comments

Comments
 (0)