APM 20 - Node JS agent not reporting metrics to remote APMIA
search cancel

APM 20 - Node JS agent not reporting metrics to remote APMIA


Article ID: 217428


Updated On:


CA Application Performance Management (APM / Wily / Introscope)


I have downloaded and installed.  NodeJS probe agent appears to connect, but we see no metrics.   Have uploaded log from probe agent (Probe-PROBE_PCF-NodeJS_csprapp.log) and compressed tar from Infra agent (InfraLogsAndConfig.tar.gz) which contains contents of logs directory and the wrapper.conf (which contains configuration - the IntroscopeAgent.profile has not been edited so have omitted that).   On the Infra agent Linux host we cn see the Infra agent is listening on port 5005:
bash-4.2$ netstat -nap | grep 5005
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0  *               LISTEN      31868/java
bash-4.2$ ps -fwwwp 31868
apmuser  31868 31865  0 15:08 ?        00:00:16 /apm/apmia/jre/bin/java -DagentManager.url.1=apm-arran-mom-test:5001 -DagentManager.url.2= -Dintroscope.agent.acc.enable=false -Dintroscope.epagent.config.httpServerPort= -Dintroscope.agent.customProcessName=CSPR_MM_DEV -Dintroscope.agent.agentName=INFRA_NodeJS_csprapp -Dintroscope.agent.connection.compatibility.version=10.7 -DagentManager.credential= -Dattribute.decoration.jsonFileName.configuration=/apm/apmia/AttributeDecorationConfig.json -Dattribute.decoration.load.configuration.from.properties=false -Xms256m -Xmx512m -Djava.library.path=lib -classpath lib/Agent.jar:lib/CollectorAgent.jar:lib/EPAgent.jar:lib/UnifiedMonitoringAgent.jar:lib/accessors-smart.jar:lib/asm.jar:lib/auto-attach-api.jar:lib/auto-attach-spi.jar:lib/com.wily.log4j.jar:lib/commons-lang3.jar:lib/dbmonitor.jar:lib/gson.jar:lib/javax.servlet-api.jar:lib/jdom.jar:lib/jetty-http.jar:lib/jetty-io.jar:lib/jetty-security.jar:lib/jetty-server.jar:lib/jetty-servlet.jar:lib/jetty-util.jar:lib/jsch.jar:lib/json-path.jar:lib/json-smart.jar:lib/mariadb-java-client.jar:lib/mssql-jdbc.jar:lib/ojdbc8.jar:lib/postgresql.jar:lib/slf4j-api.jar:lib/wrapper.jar:lib/xercesImpl.jar:lib/xml-apis.jar:core/ext/auto-attach-starter.jar -Dwrapper.key=ZXWtMufRphmubT7coTgClcYONRvn-wii -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.disable_console_input=TRUE -Dwrapper.pid=31865 -Dwrapper.version=3.5.34-pro -Dwrapper.native_library=wrapper -Dwrapper.arch=x86 -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp com.wily.introscope.agent.uma.UnifiedMonitoringAgent

So you see in the above the Java system properties defined in wrapper.conf.

When we ran he e NodeJS on a Windows machine with a local 10.7 Infra agent with NodeExtension we got metrics.

In the Infra agent before running I deleted the ACC extension (it logs lots of errors as can't get to DX Saas) and I copied in 20.6 attribute decorator extension (from a Java agent) - the attribute extensions works and ATC displays the attributes we have set.

Is this NodeJS Probe and Infra agent with Node Extension using incompatible versions?   Or ultimate aim is to have NodeJS in PCF (using build pack nodejs_buildpack_1_7_15) report to it - so if there is some version alignment required, please consider the version of probe agent in that build pack version too)


Probe metrics appear under the host where the probe is running not the host where that APMIA runs that the probe connects to.