AppMap remote recording is an easy way to record AppMaps and analyze end-user flows for applications with a web-based UI. Remote recording with the AppMap browser extension is composed of three parts:
Note: An AppMap account is required for recording AppMaps with the browser extension. If you do not plan on using the AppMap server for advanced AppMap management, we recommend that you use the AppMap code editor extensions for recording and saving AppMap files locally.
This guide assumes that you have the AppMap agent installed and running with your application server code. By following the steps shown here, you will install the browser extension and use it to create, upload and view an AppMap.
You will now see the AppMap logo displayed in your extensions area.
Don't enable AppMap remote recording in production. AppMap remote recording will serve recording results to any client request, without authentication. Remote recordings may contain sensitive data like passwords and API keys.
Add the AppMap remote recording middleware.
For example, in
require 'appmap/middleware/remote_recording' if Rails.env.development? Rails.application.config.middleware.insert_after \ Rails::Rack::Logger, AppMap::Middleware::RemoteRecording end Start your Rails server.
$ bundle exec rails server
When you run a Java process with the
appmap.jar agent loaded, it will automatically enable remote recording.
Do not load `appmap.jar` in production environments.
Creating a recording is easy.
When you stop recording, your AppMap will open in a new browser tab automatically. This may take a minute to render depending on the size of the recording you made. To make it easier to revisit your AppMap, you may want to give it a descriptive name. You can also make the AppMap public, so anyone with the link can view it.