Step-by-step instructions for configuring a project to use AppMap and using the main features.
Once you’ve configured AppMap for a project, commit the file changes to Git so that your colleagues don’t have to do the setup themselves.
The AppMap view shows all AppMaps in your open projects. You can open it from the top level menu (View -> Open view… -> AppMap), with an AppMap action or by clicking on its icon in the side bar.
AppMaps are organized by how they were created (request recording, remote recording, test case recording).
Within the AppMap tree view you can
You can also use the tree view buttons to Filter the AppMap tree by name, or search for a specific AppMap. There are also extension commands to do this.
AppMap can find automatically find software design flaws that impact security, performance, stability, and maintainability. When a problem is found, it’s listed here. Click on the problem to get detailed information about it.
All the HTTP server requests, SQL queries, packages, classes, and functions that are present in an AppMap are listed here in a tree view. You can navigate through these code objects to see what’s present in your project. Click on any code object to open the AppMaps that contain it.
NOTE: This section only applies to Java applications.
Installing the AppMap VC Code plugin adds a default Launch Configuration which supports the integrated VS Code debugger. These can be used to run your Java application code with AppMap automatically configured, saving you from manually changing your Maven or Gradle settings. This is the recommended approach for all Java users using the VS Code editor.
After installing the VS Code AppMap extension for your Java project, you will notice a new launch configuration in the .vscode
directory in your project.
Next, click on the “Run and Debug” menu option in the left hand column of VS Code
Clicking on the “Play” button next to the “Run with AppMap” launch configuration will start your Java application with the necessary AppMap configuration flags enabled by default.
When your application is running you can proceed to record AppMaps using either Requests Recording or Remote Recording
To open the list of AppMap extension actions, press CTRL+SHIFT+P
or COMMAND+SHIFT+P
on macOS and type AppMap
.
Most of the command names should be self-explanatory. Here are a few commands which are a bit more complicated:
Accounts
feature of VSCode.Guard
(Ruby), grunt
or gulp
(JS) to re-run the test cases as they are touched.You can make a remote recording from within the VSCode IDE. First, start your application with remote recording enabled. Exactly how to do this depends the language you’re using - consult the agent reference for details.
To start a recording, click the remote recording button, or use the command AppMap: Start a Remote Recording.
Interact with your app through its UI or API. Then use the stop remote recording button again, or use the command AppMap: Stop the Remote Recording.
You’ll be prompted to save the AppMap to a file, and it will be opened.
For more details about remote recording, see:
After recording AppMaps for your project, open the command pallette using CTRL+SHIFT+P
or COMMAND+SHIFT+P
on macOS, type AppMap: Generate OpenAPI
, then hit Enter
. This will open a new file with your OpenAPI definition document. Save this file locally, share with your team, or ingest as a new collection into API tools like Postman.
https://github.com/getappmap/vscode-appland