Discussion Feed

Abhimanyu.Arora

Hi Arun, This document might be helpful - https://docs.appdynamics.com/display/PRO45/AppDynamics+APIs Let me know if you have further doubts/concerns. Thanks Abhimanyu

Abhimanyu.Arora · ‎11-13-2018

Hi Abhijeet, I see you have already started a support ticket for the same, lets explore this togther there. Thanks Abhimanyu

Abhimanyu.Arora · ‎11-12-2018

Hi Stephen, Yes, appdynamics standalone machine agent, you should be able to try with a trial account. Please give a shot. Thanks Abhimanyu

Abhimanyu.Arora · ‎11-06-2018

Hi Jonathan, Can you provide a sample script that would produce this error, so that I can try it on my environment and update you with a potential solution. Thanks Abhimanyu

Abhimanyu.Arora · ‎11-06-2018

Hi Stephen, I have confirmed this with the extensions team and there is no issue installing these two extensions together however you will have to install the standalone machine agent along with it. Let know if this answers your querie or if you have any further doubts here. Thanks Abhimanyu

Abhimanyu.Arora · ‎11-06-2018

Hi Jonathan, May be you can try adding terminal encoding where you are trying to run the python script - export LC_CTYPE = en_US . UTF - 8 See if this resolves the issue. Thanks Abhimanyu

Abhimanyu.Arora · ‎11-06-2018

Hi Stephen, As far as I know, it will not be detected OTB, but you can check appdynamics extension which can help you monitor nginx and varnish. Here are the links for the same - https://www.appdynamics.com/community/exchange/ https://www.appdynamics.com/community/exchange/extension/nginx-and-nginx-plus-monitoring-extension/ https://www.appdynamics.com/community/exchange/extension/varnish-monitoring-extension/ Thanks Abhimanyu

Abhimanyu.Arora · ‎09-18-2018

Hi Necdet, The error is because appdynamics adds a special singularity header on all soap calls to make correlation between appdynamics monitored application. Since, in this case of google adward service we don't need to correlete, you can create a custom backend rule from the controller UI to turn off this singularity header for this particular call. Let me know if you need any help in doing the same. Here is a document for reference - https://docs.appdynamics.com/display/PRO45/Backend+Detection+Rules Thanks Abhimanyu

Abhimanyu.Arora · ‎08-13-2018

Hi Santosh, Unfortunately, there is nothing for now that is in the roadmap, as far as I know. But may you can give a try to glibc contained version of Alpine - https://hub.docker.com/r/frolvlad/alpine-glibc/ - if this fits your use-case. Also, a document to run glibc based programs on Alpine : - https://wiki.alpinelinux.org/wiki/Running_glibc_programs In case you wish to try these route and hitting issues, please let me know if I can be of any help. Thanks Abhimanyu

Abhimanyu.Arora · ‎08-09-2018

Hi Santosh, So here we see the problem. You are running the application on Alpine based nodejs docker image; Alpine uses musl_libc, but our agent requires glibc 2.5+. You can try using node:8-slim ,which is a debian-based image and uses glibc Thanks Abhimanyu

Date Registered	‎04-25-2018 10:09 PM
Date Last Visited	Tuesday
Total Messages Posted	20
Total Kudos Received	3

Discussion Feed

Re: List The Containers, Tiers & Nodes

Re: Not able to configure Appdynamic node js agent

Re: Varnish and NGINX together

Re: Character encoding for synthetic Python script...

Re: Varnish and NGINX together

Re: Character encoding for synthetic Python script...

Re: Varnish and NGINX together

Re: Soap call Unmarshalling Error

Re: Appdynamics agent cannot be initialized

Re: Appdynamics agent cannot be initialized