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.

Sign up

After you have installed the AppMap extension you will be prompted to sign up. This will enable AppMap Analysis and ensure that you have access to the full set of features and that they are up to date. You can log into AppMap Server with your GitHub or GitlLab account.

Navigate findings

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

JetBrains editors

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.

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.

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

JetBrians code editors

4. Map Pin indicators within the code itself

Hovering on an AppMap pin will display which findings this code is contributing to, and provide links for jumping directly to the AppMap where the problem can be explored.

Next steps

• Configuring checks

---