Red Hat SummitChapter 6. Reviewing an analysis report
After analyzing an application, you can access an analysis report to check the details of the application migration effort.
6.1. Accessing an analysis report
When you run an application analysis, a report is generated in the output directory that you specify by using the --output argument in the command line.
Procedure
Copy the path of the
index.htmlfile from the analysis output and paste it in a browser of your choice:Report created: <output_report_directory>/index.html Access it at this URL: file:///<output_report_directory>/index.htmlReport created: <output_report_directory>/index.html Access it at this URL: file:///<output_report_directory>/index.htmlCopy to Clipboard Copied! Alternatively, press Ctrl and click on the path of the
index.htmlfile.
6.2. Analysis report sections
The following are sections of an analysis report that are available after the application analysis is complete. These sections contain additional details about the migration of an application.
You can only review the report applicable to the current application.
Insights is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.
| Section | Description |
|---|---|
| Dashboard | An overview of the incidents and total story points, sorted by category. |
| Issues | A concise summary of all issues and their details that require attention. |
| Dependencies | All Java-packaged dependencies found within the application. |
| Technologies | All embedded libraries grouped by functionality. Use this report to display the technologies used in each application. |
| Insights | Information about a violation generated by a rule with zero effort. Issues are generated by general rules, whereas string tags are generated by the tagging rules. String tags indicate the presence of a technology but do not show the code location. Insights contain information about the technologies used in the application and their usage in the code. Insights do not impact the migration. For example, a rule searching for deprecated API usage in the code that does not impact the current migration but can be tracked and fixed when needed in the future. Unlike with issues, you do not need to fix insights for a successful migration. They are generated by any rule that does not have a positive effort value and category assigned. They might have a message and tag. |
6.3. Reviewing the analysis issues and incidents
After an analysis is complete, you can review issues that might appear during an application migration. Each issue contains a list of files where a rule matched one or more times. These files include all the incidents within the issue. Each incident contains a detailed explanation of the issue and how to fix this issue.
Procedure
- Open the analysis report. For more information, see Accessing an analysis report.
- Click Issues.
- Click on the issue you want to check.
- Under the File tab, click on a file to display an incident or incidents that triggered the issue.
Display the incident message by hovering over the line that triggered the incident, for example:
Use the Quarkus Maven plugin adding the following sections to the pom.xml file: <properties> <quarkus.platform.group-id>io.quarkus.platform</quarkus.platform.group-id> <quarkus.platform.version>3.1.0.Final</quarkus.platform.version> </properties> <build> <plugins> <plugin> <groupId>$</groupId> <artifactId>quarkus-maven-plugin</artifactId> <version>$</version> <extensions>true</extensions> <executions> <execution> <goals> <goal>build</goal> <goal>generate-code</goal> <goal>generate-code-tests</goal> </goals> </execution> </executions> </plugin> </plugins> </build>
Use the Quarkus Maven plugin adding the following sections to the pom.xml file: <properties> <quarkus.platform.group-id>io.quarkus.platform</quarkus.platform.group-id> <quarkus.platform.version>3.1.0.Final</quarkus.platform.version> </properties> <build> <plugins> <plugin> <groupId>$</groupId> <artifactId>quarkus-maven-plugin</artifactId> <version>$</version> <extensions>true</extensions> <executions> <execution> <goals> <goal>build</goal> <goal>generate-code</goal> <goal>generate-code-tests</goal> </goals> </execution> </executions> </plugin> </plugins> </build>Copy to Clipboard Copied!
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}