Splunk AppDynamics

Unable to Configure AppD agent on Python2.7

CommunityUser
Splunk Employee
Splunk Employee

Hi,

We are trying to install and configure the AppDynamics agent on Python(V2.7), PIP(1.4>) and the application deployment type is "Apache+mod_wsgi",

As per the steps mentioned in AppD PRO docs, we have done with installation but after configuring the variable in the "mod_wsgi" config file we had not seen the effect of the agent on the controller side.

Also, find the attachment which shows the "mod_wsgi" config file and the entries we did;

So, to configure the agent we need support.

Regards,

Ganesh Chavan

[Redacted]

^ Post edited by @Ryan.Paredez - please do not share your or other members' phone numbers for privacy and security reasons

Labels (1)
0 Karma
1 Solution

Ayush_Ghosh
Path Finder

Here is the summary of the call, which solved the issue.

  • We uninstalled the old 4.1 agent with pip uninstall appdynamics and installed the latest agent with the command pip install -U appdynamics==4.2.15.1
  • We killed the old proxy after getting the proxy pid from ps -ef | grep proxy . There should be two process to kill.
  • We bifurcated the WSGIDaemonProcess into two parts, python-path (with python source code) and python-home (with virtual environment)
  • We set proper file path for SetEnv APPD_CONFIG_FILE , which was wrong.
  • We started proxy again with the following command pyagent proxy start -c /etc/appdynamics.cfg . Please substitute with proper path in new servers.
  • Restarted Apache and with some load, it started reporting to controller.

Thanks

Ayush

View solution in original post

0 Karma

Ayush_Ghosh
Path Finder

Here is the summary of the call, which solved the issue.

  • We uninstalled the old 4.1 agent with pip uninstall appdynamics and installed the latest agent with the command pip install -U appdynamics==4.2.15.1
  • We killed the old proxy after getting the proxy pid from ps -ef | grep proxy . There should be two process to kill.
  • We bifurcated the WSGIDaemonProcess into two parts, python-path (with python source code) and python-home (with virtual environment)
  • We set proper file path for SetEnv APPD_CONFIG_FILE , which was wrong.
  • We started proxy again with the following command pyagent proxy start -c /etc/appdynamics.cfg . Please substitute with proper path in new servers.
  • Restarted Apache and with some load, it started reporting to controller.

Thanks

Ayush

0 Karma
Get Updates on the Splunk Community!

Splunk Observability Synthetic Monitoring - Resolved Incident on Detector Alerts

We’ve discovered a bug that affected the auto-clear of Synthetic Detectors in the Splunk Synthetic Monitoring ...

Video | Tom’s Smartness Journey Continues

Remember Splunk Community member Tom Kopchak? If you caught the first episode of our Smartness interview ...

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud?

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud? Learn how unique features like ...