This document explains how AppMap's remote recording feature integrates with a Tomcat application and provides a guide to troubleshooting common issues.

AppMap's remote recording functionality is enabled by a Java agent that instruments your application at runtime. When used with a Tomcat application, the agent injects a javax.servlet.Filter named RemoteRecordingFilter into the application's filter chain. This filter is responsible for intercepting and handling HTTP requests related to remote recording.

Here's a step-by-step breakdown of the process:

This guide provides solutions for common issues encountered with AppMap IDE extensions (VS Code, IntelliJ), AppMap Navie, and the AppMap Java agent. It also details how to gather debug logs and prepare a minimal reproducer for reporting bugs.

This guide shows how to deal with large AppMaps on an example of Spring PetClinic.

First, let's clone the application and open it in VSCode

$ git clone -b demo/large-appmaps https://github.com/getappmap/spring-petclinic.git
$ cd spring-petclinic
$ code .

Navie is your AI partner for code understanding, generation, and review. It uses the runtime context from AppMap and the code context from your project to provide intelligent assistance directly in your IDE.

Navie has two primary ways of understanding the code you want to discuss:

1. By Name (The Common Method)

AppMap is a powerful tool that helps developers understand and debug their code by recording its runtime behavior. This guide details the four primary methods for recording AppMap data: test recording, request recording, remote recording, and process recording. Understanding these methods will enable you to choose the most effective approach for your specific needs.

What it entails: Test recording is the most common and often recommended method for generating AppMaps. It integrates with your existing testing frameworks (like JUnit or TestNG for Java) to automatically create an AppMap for each test case that is executed. The AppMap agent is enabled when you run your tests, and it captures the code execution, including method calls, parameters, return values, and interactions with external services like databases and web services.

When to use it:

This is a quick reference guide for using the AppMap agent for Java.

The AppMap agent is a .jar file that attaches to the JVM. The AppMap IDE extensions (for VS Code or IntelliJ) will automatically download it for you. You can also use the Maven or Gradle plugins.

This is a quick reference guide for using the AppMap agent for Python.

Install the appmap package into your project's virtual environment.

pip:

At AppLand we're currently working on ways in which we can visualize how changes to the code affect program design and execution. But it turns out you don't need any fancy visuals to be able to tell something useful.

(BTW, see the whole code gallery!)

If you're not familiar with AppLand, at the very basic level, it allows you to record program execution traces. These traces can then be processed to surface interdependencies between code artifacts (such as classes, objects