@appland/appmap-agent-js

Getting started with appmap-agent-js

appmap-agent-js is a JavaScript recording agent for the AppMap framework.

Introduction

appmap-agent-js records AppMaps from Node.js processes when they run. There are two recommended strategies for recording AppMaps when getting started:

1. Record mocha test cases when they run.
2. Record Node.js processes using start/stop controls via http calls to web endpoints. These are implemented by the AppMap agent to let users control the recording remotely.

appmap-agent-js starts the test and application processes that will be recorded.

Installation and setup

Requirements

Supported platforms:

• Unix-like os, tested on Linux and macOS; Windows is currently not supported
• Node.js 14 or 16
• Express.js
• git is highly recommended
• mocha >= 8.0.0 is requried for recording AppMaps from test cases (earlier versions do not support required root hooks)

Please open a new GitHub ticket if your application does not satisfy the criteria or if you experience any problems with the agent.

Installation

Run this command in your Node.js project folder (where package.json is located):

npx @appland/appmap install

You will be guided through a series of steps for installing and configuring the agent.

To use remote recording, and view and interact with recorded AppMaps, we recommend installing the AppMap extension for popular code editors:

• AppMap in VS Code Marketplace
• AppMap in JetBrains Marketplace

Initial configuration

The agent requires a valid configuration in appmap.yml file. The install command creates a default appmap.yml file by scanning the project directories. We recommend that you review the generated appmap.yml file and confirm your application name and a list of directories that will be recorded.

For projects with JavaScript source maps: add paths to sources to be recorded. For example:

name: MyApp
packages:
  - path: src/server/controllers
  - path: src/server/data
  - path: src/server/lib
  - path: src/server/models
  - path: src/server/routes

For projects without JavaScript source maps: include build folders. For example:

name: MyApp
packages:
  - path: dist/controllers
  - path: dist/data
  - path: dist/lib
  - path: dist/models
  - path: dist/routes

If you aren't sure which option to take, start with both source and build folders and optimize the appmap.yml file later.

Recording AppMaps

Once appmap.yml is configured for your project, you're ready to record AppMaps.

Recording mocha test cases:

1. Validate that the tests run prior to recording AppMaps.
2. Run appmap-agent-js with the mocha command and its parameters following the -- delimiter. For example:

npx appmap-agent-js -- mocha test/**/*.ts

1. appmap-agent-js will run the tests. When the tests are complete, the AppMaps will be stored in the default output directory tmp/appmap/mocha.

Recording Node.js processes with remote recording:

1. Run appmap-agent-js with the application-starting command and its parameters following the -- delimiter. For example:

npx appmap-agent-js -- node app/main.js --param1 hello --param2=world

1. appmap-agent-js will start the app and inject itself in its http stack. It will listen for remote recording requests on all http ports of the application.
2. Start the remote recording:
   • in VS Code
   • in JetBrains IDEs
   • with curl
3. Interact with your application or service to exercise code included in appmap.yml
4. Stop the recording and save the new AppMap to disk.

Viewing AppMaps

Recorded AppMap are saved as .appmap.json files in the project folders (default location: tmp/appmap.)

Follow the documentation for your IDE to open the recorded .appmap.json files:

• in VS Code
• in JetBrains IDEs

Frequently used parameters

The most frequently used appmap-agent-js parameters are:

• --recorder=[mocha|remote|process] : process recorder
  • default recorder is inferred from the starting command:
    • mocha if the the command contains mocha
    • remote in all other cases
  • mocha recorder records AppMaps from test cases automatically
  • remote recorder has to be started and stopped manually with http requests
  • process recorder records entire processes automatically, from start to finish
    • Warning: AppMaps recorded with the process recorder can be excessively large and noisy.
• --command="_start command_" : alternate method of specifying the app- or tests-starting command, wrapped in quotes
• --log-level=[debug|info|warning|error] : defaults to info
• --log-file=_file_ : location of log file, defaults to stderr
• --appmap-dir=_directory_ : location of recorded AppMap files, default is tmp/appmap.

Example

npx appmap-agent-js --recorder=mocha --command="mocha test/**/*.ts" --log-level=error

Next steps

• appmap-agent-js reference documentation

Changelog

11.3.0 (2022-09-09)

Bug Fixes

• add body to manufactured http events for completion (b3b05cf)
• adhere to the appmap spec for error format (3ee5da4)
• conform to appmap spec for metadata git (e524791)
• group frame in trace post-processing (b3fbe60)
• handle http headers which are not strings (499d204)
• insert symbolic link instead of copying main file (b905dba), closes /github.com/vercel/next.js/blob/7e5cb510c4155572d0b251db34845d34fd078480/packages/next/lib/get-project-dir.ts#L3
• make sure all payload field satisfy the schema (8d28927)
• make sure http response status is in the right format (96bbcde)
• more lenient monkey-patching (cb392b3)
• move recording of server side request to capture initial event (cdf65c1)
• no longer overwrite configuration.log.level with error (61d67c7)
• properly report unknown configuration field (1728c56)
• show the children of excluded functions (c41b3ae)
• source-map is not a dev-only module (fa278b8)

Features

• remove recording methods from the API (aa85b7d)
• support eval instrumentation (02821b1)
• write appmaps with formatted json (28b1df0)