This looks like a bug in the new version 20.6. On every flow map in the dashboard or in the snapshot,  I keep seeing "ui:ms_transactionExitPointType_null" appearing on the link between the tiers. Does anybody know why is this happening? ... View more

Hi, I would like to know the recommended way to monitor some processes or services inside the OS. Can this be achieved within a regular AppDynamics controller health rules, or do I have to search through extensions and try to find something in there? For instance, if a service or process gets stopped I would like to have a health rule which would trigger an immediate event, put this on the dashboard etc. ... View more

I would like to understand what is the EMEA address space used for SaaS controllers. I am looking at the document: https://docs.appdynamics.com/display/PAA/SaaS+Domains+and+IP+Ranges but I am not sure if address ranges mentioned in the "AppD Data Center" are valid for all the regions in the world. Because, when I open "EMEA" tab, there are no IP addresses in there. It says "AppDynamics will provide a unique set of IP addresses at the time of provisioning the Controller within AWS." What does this mean? Are these addresses provided at the provisioning moment from the same address block mentioned before, or not? I need to know this because our customers want to allow outbound connectivity to certain IP addresses - they don't want to generally open port 443 for the whole internet. ... View more

I am trying to figure out exactly how many licenses do I need when using .net core (microservices) agent on a windows host. So, having several APIs on the same IIS, all using .net core and these APIs are already up and running. By reading through your docs and knowledge base, I am not able to precisely get the answer. Here's the thing. In all of your license documents you are not mentioning windows host deployment types. Take a look at this: In the case of Microservice Agents (including .NET), 5 Agents consume 1 APM_ANY license. As mentioned in our License Entitlements and Restrictions documentation, a Microservices product has the same entitlement as 5 APM Any Language units, restricted to use with the following:  Docker Containers all CloudFoundry-based providers Redhat OpenShift Heroku Dyno Microsoft Azure App Services (including Azure WebApps, Azure WebJobs and Azure API Apps) Microsoft Azure Service Fabric No Windows there. So, I am afraid that each and every deployment of .net core agent will take one license which will be a disaster compared to your regular .net agent license model. Imagine 10 different APIs on a single IIS. In the regular model, this would consume just one agent. If what I copied earlier in the text is true for this case as well, then I would need just two licenses which is also fine. But if I have to have 10 licenses for 10 APIs... forget it... ... View more

After upgrading the AppD agents, we are having impact the services which are using Blaze licence. JVM's are failing to load the service components during startup. After backing out the agent upgrade the Services/JVM's started with out any issues.  Could you please let us know if there are any known issues with incompatibility ... View more

It was working fine. All of a sudden we are not getting e-mail notifications for our app transaction & HR violation notification e-mails. I can see below error in SaaS controller UI. Action Exception: Failed to send policy notification email. Empty email configuration. (As shown in below picture) Any one got like this error in past? ... View more

npm install appdynamics@4.5.13 fails Looks like some form of SSL problem. Only with the appdynamics package, all other packages install OK. npm WARN deprecated set-immediate@0.1.1: Use `setimmediate` instead npm ERR! code ECONNREFUSED npm ERR! errno ECONNREFUSED npm ERR! FetchError: request to https://cdn.appdynamics.com/packages/nodejs/4.5.13.0/appdynamics-libagent-node.tgz failed, reason: connect ECONNREFUSED 0.0.0.0:443 npm ERR! at ClientRequest.req.on.err (/usr/local/lib/node_modules/npm/node_modules/node-fetch-npm/src/index.js:68:14) npm ERR! at ClientRequest.emit (events.js:198:13) npm ERR! at TLSSocket.socketErrorListener (_http_client.js:392:9) npm ERR! at TLSSocket.emit (events.js:198:13) npm ERR! at emitErrorNT (internal/streams/destroy.js:91:8) npm ERR! at emitErrorAndCloseNT (internal/streams/destroy.js:59:3) npm ERR! at process._tickCallback (internal/process/next_tick.js:63:19) npm ERR! { FetchError: request to https://cdn.appdynamics.com/packages/nodejs/4.5.13.0/appdynamics-libagent-node.tgz failed, reason: connect ECONNREFUSED 0.0.0.0:443 npm ERR! at ClientRequest.req.on.err (/usr/local/lib/node_modules/npm/node_modules/node-fetch-npm/src/index.js:68:14) npm ERR! at ClientRequest.emit (events.js:198:13) npm ERR! at TLSSocket.socketErrorListener (_http_client.js:392:9) npm ERR! at TLSSocket.emit (events.js:198:13) npm ERR! at emitErrorNT (internal/streams/destroy.js:91:8) npm ERR! at emitErrorAndCloseNT (internal/streams/destroy.js:59:3) npm ERR! at process._tickCallback (internal/process/next_tick.js:63:19) npm ERR! message: npm ERR! 'request to https://cdn.appdynamics.com/packages/nodejs/4.5.13.0/appdynamics-libagent-node.tgz failed, reason: connect ECONNREFUSED 0.0.0.0:443', npm ERR! type: 'system', npm ERR! errno: 'ECONNREFUSED', npm ERR! code: 'ECONNREFUSED', npm ERR! stack: npm ERR! 'FetchError: request to https://cdn.appdynamics.com/packages/nodejs/4.5.13.0/appdynamics-libagent-node.tgz failed, reason: connect ECONNREFUSED 0.0.0.0:443\n at ClientRequest.req.on.err (/usr/local/lib/node_modules/npm/node_modules/node-fetch-npm/src/index.js:68:14)\n at ClientRequest.emit (events.js:198:13)\n at TLSSocket.socketErrorListener (_http_client.js:392:9)\n at TLSSocket.emit (events.js:198:13)\n at emitErrorNT (internal/streams/destroy.js:91:8)\n at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)\n at process._tickCallback (internal/process/next_tick.js:63:19)', npm ERR! parent: 'appdynamics' } npm ERR! npm ERR! If you are behind a proxy, please make sure that the npm ERR! 'proxy' config is set properly. See: 'npm help config' ... View more

We have one application (App A) which calls another app (App B) via HTTP(s) API. Both apps have AppD Machine and App agents installed. After performing an upgrade on App A from Java 1.8 to OpenJDK11, we are no longer seeing the interaction between App A & B on the Application Flow Map.  Any idea why an HTTP API call would no longer show up on our Application Flow Map after a JDK upgrade? We know for certain the call is still being made, otherwise there'd be a much larger fire to put out. App A is custom Java app running on OpenJDK11 This is what has changed App B is a COTS Java app running on Java 1.8 App A connects to App B via HTTP(s) API call Both App A and App B have machine agents installed and running Both are running on Java 1.8 ... View more