In your code editor

When there are AppMaps available in your project, AppMap Runtime Analysis will immediately scan them to detect flaws in the code. These flaws are surfaced as findings and are displayed in your code editor as you work so that they can be addressed before they are propagated to Test or Production environments.

AppMap makes information about findings available in four places:

  1. The Runtime Analysis step of the setup instructions
  2. The Runtime Analysis sidebar pane
  3. The Problems tab
  4. Map Pin indicators within the code itself

1. The Runtime Analysis step of the setup instructions

Visual Studio Code

the last step of setup instructions in Visual Studio Code

JetBrains editors

the last step of setup instructions in JetBrains

2. The Runtime Analysis sidebar pane

In Visual Studio Code, findings are displayed In the Runtime Analysis sidebar pane sorted by impact category and type.

Runtime analysis sidebar findings

Clicking the ‘Overview’ link in the Runtime Analysis sidebar will open the ‘Runtime Analysis Summary’ window which contains a high-level roll up of findings for a particular project.

Runtime analysis overview dashboard

3. The Problems tab

Findings are displayed in the ‘Problems’ window, in-line with other project-related errors and issues. Every instance of a finding presented in the problems tab includes metadata related to the issue as well as linkage to the affected areas of the code.

Visual Studio Code

Runtime analysis in Visual Studio Code Problems tab

JetBrians code editors

Runtime analysis in JetBrains Problems tab

4. “Squiggle” indicators within the code itself

A “code squiggle” indicates that there is a finding associated with that line of code. However over the squiggle to open a detailed description of the finding.

Runtime analysis map pin indicator

Next steps


Was this page helpful? thumb_up Yes thumb_down No
Thank you for your feedback!