Splunk AppDynamics

NodeJS Appdynamics initialization error

pothuraju_chebe
New Member

I'm using nodejs appdynamics agent, when deployed in AWS EC2 Container application is not up because of this error.

Even in local when tried to run this, I'm stuck with same error. Please help!

docker container run <<DOCKERIMAGE>>

TypeError: Cannot read property 'logError' of undefined
at LibagentConnector.logError (/usr/src/app/node_modules/appdynamics/lib/libagent/libagent-connector.js:367:17)
at Logger.error (/usr/src/app/node_modules/appdynamics/lib/core/logger.js:167:28)
at Agent.init (/usr/src/app/node_modules/appdynamics/lib/core/agent.js:319:17)
at AppDynamics.self.(anonymous function) [as profile] (/usr/src/app/node_modules/appdynamics/lib/core/agent.js:610:26)

Labels (1)
0 Karma

Piyush_Mundra
Communicator

Hi Pothuraju,

This issue comes up when the Node version for which the agent was installed differs in the environments. The Node agent has some native dependencies so I suggest installing the agent in the docker container rather than pushing the agent files with the project files. This will ensure the correct agent dependency files would be installed in the docker environment.

Best Regards,

Piyush

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Fuel Your Journey: What’s Waiting for You at the .conf26 Acceleration Station

Navigating the show floor at .conf26 isn't just about keynotes and technical breakout sessions; it's also ...

Join the Final Session of the Data Management & Federation Bootcamp Series

Over the past three sessions of the Data Management & Federation Bootcamp Series, we've explored how to build ...

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...