On this page:

Related pages:

Search Node.js Agent topics:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
18 rates

This page introduces the Node.js Agent. With the Node.js agent and AppDynamics, you get automated transaction detection and correlation across your Node.js enabled environment. 

Node Naming for Node.js Agents

Each instrumented Node.js process corresponds to a node in the AppDynamics model.

The nodes are named by combining the prefix that you specify for the nodeName in the requires statement that you add to the application source code when you install the Node.js agent with a hyphen and a digit. 

 For example, if you designate a prefix of MyNode for the nodes in the MyTier tier, the nodes in that tier are named MyNode-0, MyNode-1, MyNode-2 and so on.

Node.js Agent and the Java Proxy

The agent communicates with a Java proxy that handles the communication between the Node.js Agent and the AppDynamics Controller. The proxy reports the performance metrics to the Controller, where the data is stored, baselined, and analyzed. You can access this performance data interactively using the Browser UI or programmatically using the AppDynamics REST API.

The proxy component is automatically started when you start the Node.js Agent.


Instrument a Node.js Application Overview

The Getting Started Wizard walks you through configuration steps and helps you download the agent. To access it, in the Home page of the controller click Getting Started and then Node.js.

The wizard provides the minimum information that the agent needs to communicate with the AppDynamics Controller: controller host and port, optionally SSL, application name and tier name.

Watch the Video

For full-screen viewing, click Start Monitoring Node.js Applications.