Merge pull request #793 from reportportal/develop

Release

docs/analysis/PatternAnalysis.mdx

@@ -5,48 +5,88 @@ sidebar_label: Pattern Analysis
 
 # Pattern Analysis
 
-Pattern analysis is a feature that helps you to speed up test failure analysis by finding common patterns in error logs.
+Pattern Analysis is a feature that helps you to speed up test failure analysis by finding common patterns in error logs.
 
-## Types of Pattern Analysis
+## How to run Pattern Analysis
 
-**String** – any problem phrase.
+You can run Pattern Analysis automatically or manually.
 
-<MediaViewer src={require('./img/PatternAnalysis/PatternAnalysisString1.png')} alt="Pattern Analysis String rule" />
+To run Pattern Analysis **automatically**:
 
-<MediaViewer src={require('./img/PatternAnalysis/PatternAnalysisString2.png')} alt="Pattern Analysis String in the logs for automated defect triaging" />
+1. Go to the Project Settings.
 
-**Regex** – regular expression.
+2. Open Pattern-Analysis tab.
 
-<MediaViewer src={require('./img/PatternAnalysis/PatternAnalysisRegex1.png')} alt="Pattern Analysis Regex rule" />
+3. Check the "Auto Pattern-Analysis" checkbox.
 
-<MediaViewer src={require('./img/PatternAnalysis/PatternAnalysisRegex2.png')} alt="Pattern Analysis Regex in the logs for automated bug triage process" />
+4. Create rule.
+
+5. Run a launch.
+
+6. After launch finish, automatic Pattern Analysis will occur.
+
+<MediaViewer src={require('./img/PatternAnalysis/PatternAnalysis1.png')} alt="Run Pattern Analysis automatically" />
 
 :::note
-It would be better to use STRING rule instead of REGEX rule in all possible cases to speed up the Pattern Analysis processing in the database. As a result, you can get your analysis completed faster using the STRING patterns rather than REGEX and reduce the database workload.
+Automatic Pattern Analysis is activated by default.
 :::
 
-## Use case 1:
+In case automatic Pattern Analysis is turned off, you can run **manually** from the menu next to a particular launch:
+
+<MediaViewer src={require('./img/PatternAnalysis/PatternAnalysis2.png')} alt="Run Pattern Analysis manually" />
+
+## How to create rules for Pattern Analysis
+
+To create rule:
+
+1. Go to the Project Settings.
+2. Open Pattern Analysis tab.
+3. Click ‘Create Pattern’ button.
+4. Fill in the form.
+5. Create ‘Create’ button.
+
+<MediaViewer src={require('./img/PatternAnalysis/PatternAnalysis3.png')} alt="Create Pattern button" />
+
+<MediaViewer src={require('./img/PatternAnalysis/PatternAnalysis4.png')} alt="Creating Pattern Analysis rule" />
 
-**Problem:** A user knows the several common problems why test cases fail. During tests run a lot of test have failed. A user need to check logs a of tests to know by what reason test cases have failed.
+## Types of Pattern Analysis rules
 
-**Solution:** Create a pattern rules for all common reasons which contains a problem phrase (for example: *"Expected status code `<404>` but > was `<500>`"* or "*Null response"*) or with Regex query (for example: java:[0-9]*). Switch On a pattern analysis.
-Launch a test run.
-So that the ReportPortal systems finds all failed items which have known patterns in error logs and marks them with a label with pattern name.
-Find all items failed by the same reason by choosing a filter by Pattern Name on the Step view.
-Add The most popular pattern widget (TOP-20) and track the TOP-20 the most popular reason of test failing in the build.
+There are two types of Pattern Analysis rules:
+
+1. String – any problem phrase.
+
+<MediaViewer src={require('./img/PatternAnalysis/PatternAnalysis5.png')} alt="String Pattern Analysis rule" />
+
+<MediaViewer src={require('./img/PatternAnalysis/PatternAnalysis6.png')} alt="Example of String Pattern Analysis rule" />
+
+2. Regex – regular expression.
+
+<MediaViewer src={require('./img/PatternAnalysis/PatternAnalysis7.png')} alt="Regex Pattern Analysis rule" />
+
+<MediaViewer src={require('./img/PatternAnalysis/PatternAnalysis8.png')} alt="Example of Regex Pattern Analysis rule" />
+
+:::note
+It would be better to use STRING rule instead of REGEX rule in all possible cases to speed up the Pattern Analysis processing in the database. As a result, you can get your analysis completed faster using the STRING patterns rather than REGEX and reduce the database workload.
+:::
 
-<MediaViewer src="https://youtu.be/K3Wk_S4Cuko" alt="Pattern Analysis launched Automatically" type="video" />
+## Use case 1
 
-## Use case 2:
+**Problem:**<br/>
+A user is aware of several common reasons why test cases fail. During a test run, many tests have failed, and the user needs to check the logs to identify the reasons behind the failures.
 
-**Problem:** Test run has finished. A user found that more than 3 items have failed by the same reason. And he want to find all such items.
+**Solution:**<br/>
+Create pattern rules for all common failure reasons, which include specific problem phrases (e.g., `Expected status code <404> but was <500>` or `Null response`) or use Regex queries (e.g., `java:[0-9]*`). Enable pattern analysis and launch a test run. This way, the ReportPortal system can identify all failed items that match known patterns in the error logs and label them with the corresponding pattern name. To find all items that failed for the same reason, apply a filter by ‘Pattern Name’ in the Step view. Additionally, add a ‘Most Popular Pattern’ widget to track the top 20 most frequent reasons for test failures in the build.
 
-**Solution:** Create a new pattern rule on Project Settings. Launch a pattern analysis manually for one launch.
-name.
-Find all items failed by the same reason by choosing a filter by Pattern Name on the Step view.
+<MediaViewer src={require('./img/PatternAnalysis/PatternAnalysis9.png')} alt="Pattern Name filter" />
 
-<MediaViewer src="https://youtu.be/_BhG0Tu4H_I" alt="Pattern Analysis launched Manually" type="video" />
+<MediaViewer src={require('./img/PatternAnalysis/PatternAnalysis10.png')} alt="Select pattern name" />
 
+## Use case 2
 
+**Problem:**<br/>
+The test run has finished, and the user notices that more than three items have failed for the same reason. The user wants to find all such items.
 
+**Solution:**<br/>
+Create a new pattern rule in the Project Settings. Manually launch a pattern analysis for a specific test run. Use the ‘Pattern Name’ filter in the Step view to find all items that failed for the same reason.
 
+<MediaViewer src="https://youtu.be/W7qMwhLpIFI" alt="Pattern Analysis launched Manually" type="video" />

docs/installation-steps-advanced/ScalingReportPortalServices.md

@@ -0,0 +1,41 @@
+---
+sidebar_position: 13
+sidebar_label: Scaling ReportPortal services
+---
+
+# Scaling ReportPortal services
+
+ReportPortal supports dynamic scaling of its API service during runtime to efficiently manage varying loads. This guide provides instructions on how to scale the API service up or down and discusses the implications of asynchronous reporting and queue management in RabbitMQ while scaling.
+
+ ReportPortal also supports the scaling of UAT and UI services. However, it's not recommended to scale the Jobs service due to potential conflicts with cleaning cron jobs, which may lead to database locking issues.
+
+To effectively scale ReportPortal, you need to follow these steps:
+
+1. **Additional resources**: Increase capacity by deploying more instances or by enhancing the resources (CPU and memory) of existing ones.
+2. **Load Balancing**: The Traefik (for Docker) and Ingress Controller (for Kubernetes) are already set up to automatically distribute incoming requests among all active services.
+3. **AMQP settings:** Performance improvements can be achieved by increasing the queue count and adjusting the prefetch count per consumer. These adjustments allow for more efficient processing and resolution of messages within the queues. For more detailed information, refer to the article [Asynchronous Reporting](/developers-guides/AsynchronousReporting/#exchanges-and-queues-for-reporting).
+
+## Kubernetes Configuration
+
+1. **Scaling Services**: To scale your [ReportPortal services in Kubernetes](https://github.com/reportportal/kubernetes), you need to increase the replica count parameter in the `values.yaml` file for the required services. For example, to scale the API service, adjust the `replicaCount` as shown below:
+
+   ```yaml
+   serviceapi:
+     replicaCount: 2
+   ```
+
+2. **Load Balancing**: The Ingress Controller is already set up to automatically distribute incoming requests among all active services. However, to enhance control over idle TCP connections adjust the IDLE Timeout value to `300`.
+
+## Docker Configuration
+
+1. **Scaling Services**: To scale your [ReportPortal services in Docker](https://github.com/reportportal/reportportal/blob/master/docker-compose.yml), you need to add a replica parameter in the `docker-compose.yml` file for the required services. For example, to scale the API service, adjust the `replicas` as shown below:
+
+   ```yaml
+   services:
+
+     api:
+       deploy:
+         replicas: 2
+   ```
+
+2. **Load Balancing**: The Teafik is already set up to automatically distribute incoming requests among all active services.

docs/installation-steps-advanced/UpgradingPostgreSQLForReportPortalV24.2AndLater.md

@@ -0,0 +1,64 @@
+# Upgrading PostgreSQL for ReportPortal v24.2 and later
+
+:::important
+This guide is intended for users planning to upgrade from Postgres 12 to a newer version, starting with ReportPortal version 24.2.
+:::
+
+This guide will walk you through backing up your current PostgreSQL database, removing existing containers and volumes, downloading the latest release, and restoring the PostgreSQL dump.
+
+## Step 0: Backup Postgres and Storage
+Before proceeding, ensure you have a complete Postgres database and Storage backup.
+
+## Step 1: Create a Dump of Database
+Run the following command to create a dump of your current PostgreSQL database:
+
+```bash
+docker exec -t postgres pg_dump -U rpuser -d reportportal > reportportal24_1_postgres12_dump.sql
+```
+
+## Step 2: Remove All Containers
+Shut down and remove all containers:
+
+```bash
+docker compose -p reportportal down
+```
+
+## Step 3: Remove Postgres Volume
+Remove the Postgres volume to ensure a clean state for the new database:
+
+```bash
+docker volume rm reportportal_postgres
+```
+
+## Step 4: Download Latest Release
+Fetch the latest `docker-compose.yml` file to get the most recent version of ReportPortal:
+
+```bash
+curl -LO https://raw.githubusercontent.com/reportportal/reportportal/refs/heads/master/docker-compose.yml
+```
+
+## Step 5: Run Postgres Container
+Start only the Postgres container to prepare for database restoration:
+
+```bash
+docker compose -p reportportal up -d postgres
+```
+
+## Step 6: Restore Postgres Dump
+Restore the database dump into the new Postgres container:
+
+```bash
+docker exec -i -e PGPASSWORD=rppass postgres psql -U rpuser -d reportportal < reportportal24_1_postgres12_dump.sql > upgrade_db.log 2>&1
+```
+
+## Step 7: Run ReportPortal
+Bring up all the services for ReportPortal:
+
+```bash
+docker compose -p reportportal up -d
+```
+
+## Final Notes
+- Verify that all services are running correctly using `docker ps` or checking the logs.
+- Keep the log file `upgrade_db.log` for any potential troubleshooting.
+- Regular backups are essential. Make sure to have a reliable strategy in place.

docusaurus.config.js

@@ -525,7 +525,7 @@ const config = {
             from: '/installation-steps/ReportPortal23.1FileStorageOptions',
           },
           {
-            to: '/installation-steps-advanced/ScalingUpReportPortalAPIService',
+            to: '/installation-steps-advanced/ScalingReportPortalServices',
             from: '/installation-steps/ScalingUpReportPortalAPIService',
           },
           {