MTA-3102-app insights section added

Author: Vibhuti Sodhi

docs/topics/mta-review-reports.adoc

@@ -77,6 +77,9 @@ The top navigation bar lists the various reports that contain additional details
 | Issues
 | Provides a concise summary of all issues that require attention.
 
+| Insights
+| Provides information about the technologies used in the application and their usage in the code. However, these Insights do not impact the migration.
+
 | Application details
 | Provides a detailed overview of all resources found within the application that may need attention during the migration.
 
@@ -152,6 +155,56 @@ image::3-5-expanded-issue.png[Expanded rule in the issues report]
 
 Issues are sorted into four categories by default. Information on these categories is available at ask Category.
 
+
+=== Insights
+
+Insights provide helpful information about the technologies used in the application and their usage in the code.
+For example, a rule searching for a 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 issues, insights do not need to be fixed for a successful migration. They are generated by any tagging or non-tagging rule and do not have an effort and category assigned. They might have a message and tag.
+
+[NOTE]
+=====
+Insights are generated automatically, if applicable or present. However, you must run the application analysis by using the CLI because MTA 7.1 does not support their generation through the UI.
+=====
+
+You can view Insights in the Static report under the Insights tab and in the analysis output under the Insights section.
+
+.Example: Insights generated by a tagging rule with undefined effort and category
+
+[source,terminal]
+----
+- customVariables: []
+  description: Embedded library - Apache Wicket
+  labels:
+  - konveyor.io/include=always
+  links: []
+  ruleID: mvc-01000
+  tag:
+  - Apache Wicket
+  - Embedded library - Apache Wicket
+  when:
+    builtin.file:
+      pattern: .*wicket.*\.jar
+----
+
+.Example: Insights generated by a non-tagging rule with zero effort and no category
+
+[source,terminal]
+----
+- category: potential
+  customVariables: []
+  description: RESTful Web Services @Context annotation has been deprecated
+  effort: 0
+  message: Future versions of this API will no longer support `@Context` and related
+    types such as `ContextResolver`.
+  ruleID: jakarta-ws-rs-00001
+  when:
+    java.referenced:
+      location: ANNOTATION
+      pattern: jakarta.ws.rs.core.Context
+----
+
 === Application details report
 
 Access this report from the dashboard by clicking the *Application Details* link.