Thanks Cody, but I believe the developer is missing my point.
The "old" ASP.NET applications offer out-of-the-box transformations for XML conifguration files but not for JSON files. This means the target AppDynamics controller name cannot be changed for build configurations as part of the MSbuild process, e.g. UAT or PROD build profiles. I've attached two screenshots showing the issue created by the latest 4.4 release.
Note, if this was a .net core project then it wouldn't be a problem as they do support JSON config transformations.
As far as I'm aware the fact the target deployment is Azure makes zero difference.
For now the client has rolled back to version 4.3 of the nuget package where AppDynamics still use the supported XML transformations. T here will come a time when they'll need to upgrade to the latest version resulting in them adding additional process to transform JSON files though.
Thanks again, Ben.
... View more
A client of ours today upgraded their Azure agent nuget version to 4.4 which removed the previous AppDynamics XML configuration file into a JSON file. Just out of curiosity I'm wondering why this approach has been taken?
Reason for asking is that as far as I'm aware, out of the box within ASP.NET (note, this is not a .net core project) JSON configuration files do not support transformation as they would with say a "web.config" or "app.config" file. Please do let me know if I'm wrong though.
If I'm right, AppDynamics customers not using CI CD processes won't necessarily be expecting this configuration shift leaving them confused.
Also, your latest 4.4 documentation for the Azure app service has the wrong configuration paths:
From testing it they go into ~/"AppDynamics/AppDynamicsConfig.json".
... View more
Unfortunately it appears to have gone down again, albeit it looks to be a different issue?
I've uploaded the last agent log the customer sent to me (before the issue was resolved late yesterday).
If you could please check to see if all is OK at the backend, I'll also check with the client to see if they're aware and to see if they've made any other changes.
... View more
We have a client trialing AppDynamics and currently we're not able to see database lists or executed SQL statements etc. The client has sent us the DB logs from AppDynamics where we can see various errors similar to the below:
[Event-Uploader-Scheduler-2] 18 Jul 2017 14:41:07,799 WARN DBMeasurementUploader - Fail to upload Query Stats Measurements: com.singularity.ee.rest.ResponseReadException: Error in controller in processing binary request Write Query Stats - null at com.singularity.ee.rest.controller.request.ABinaryControllerRequest.<init>(ABinaryControllerRequest.java:65) at com.singularity.ee.rest.controller.request.dbmon.WriteQueryStatsRequest.<init>(WriteQueryStatsRequest.java:30) at com.singularity.ee.agent.dbagent.task.reporter.DBMeasurementUploader.uploadrQueryStats(DBMeasurementUploader.java:100) at com.singularity.ee.agent.dbagent.task.reporter.DBMeasurementUploader.run(DBMeasurementUploader.java:117) at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335) at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152) at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:119) at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:206) at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:236) at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694) at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726) at java.lang.Thread.run(Unknown Source)
The client is question is using your SaaS platform and from looking at other similar support tickets I believe we may need your help to get this up and running correctly? Unfortunately the customer has 10 days left in their trial period so time is tight.
Please let me know what we need to do to resolve this.
... View more