hello,

I activated the raw sql capture however i would like to see aggregated result in the slowest Db calls.

For instance we are using stored procedure so i do not want to see separated rows when parameters change.

do you have any solution ?

thank you.

Hi,

I also opened a trial account and gets an error :

"Controller communication failed. Details: Unable to connect to the remote server
Please use certmgr.msc to add Controller Certification Authority certificate to
"Trusted Root Certification Authorities" at computer account (system) level."

I also get it when I tried to turn off SSL in the controller side, and change the port to 80.

Till now I couldn't find any simple documentation regarding where to import the AppDynamics certificate from.

Pretty dissappointing onboarding experience.

Thanks.

Already saw this guide, unfortunately it didn't help.

The only relevant paragraph which relates to my case is the following:

"

• The AppDynamics SaaS Controller uses certificates signed by DigiCert. In some cases, SaaS customers must import the DigiCert root certificates into the Windows Trusted Root Certification Authorities store.

"

There's no explanation regarding how to do so, and besides, I have 3 DigiCert certificates in the Trusted Root Certification Authorities list:

DigiCert Assured ID Root CA

DigiCert Global Root CA

DigiCert High Assurance EV Root CA

Using Windows 8.1 Enterprise.

I worked with AppD support and they provided the below information which has worked for us:

Hi there! 

The error you provided is a bit misleading (we're working to make it more clear).

The important part of the meessage is this: Details: Unable to connect to the remote server.  This means that there is no network connectivity from your Agent to the SaaS controller. If SSL negotiation was the issue, you'd see an error message that looked like this "The remote certificate is invalid according to the validation procedure." The majority of customers won't need any special SSL configuration because most up to date Windows servers  trust Digicert as a Certificate Authority by default. 

That said, to troubleshoot this, please verify that you can access your controller using the same address/port using Internet Explorer from the server that the agent is installed on.  If this works,  it's very likely the Web Browser on your server is using a Proxy which will need to be added in the Agent Configuration Wizard so that the agent can use it as well. If this doesn't work, you'll need to talk to your Network team to ensure there is network connectivity from the Agent server to the Controller.

I hope this helps!

Thanks,

Matt

I need to get the session information through Rest API of app dynamics using Python.

Hi,

We  have a node application which we want to profile. But when we tried, Appdynamics could not provide the breakdown for the full call. If you could see the attached snapshot, AD is giving the call graph for 2 ms whereas the overall call is about ~1099ms.Can you please help me to understand how can i get the break down for 1099 ms? Let me know if you need any other details. Thank you.

Below are the details of my AD :

Controller: https://paypalnodejs1.saas.appdynamics.com/

Agent : 4.2.7.0

Hi,

Thanks for your reply.

Connection from browser (both IE and Chrome) succeeds - it leads to the URL https://soluto.saas.appdynamics.com/controller/#/location=AD_HOME_OVERVIEW

However, in the .NET Agent configuration wizart, I still get an error: "Controller communication failed. Details: The remote server returned an error: (401) Unauthorized."

I checked with our network team, we don't have any proxy configuration. Also, there are no blocks from my machine in the Firewall log.

Ofer

Hey all,

I've been trying to search some documentation about connecting Appdynamics alerts to other monitoring tools (in my case 'Netcrunch'). I'm pretty sure I've read some documentation about it somewhere but I can't seem to find it anymore. Is there such a thing and if so where can I find it?

thanks.

Regards,

Adriaan

After talking with Support, here is a response that was given for future reference:

There is no hard core limit per machine agents but may be we would hit the default max metric limit of an machine agent .  That should not be problem if your controller has the capacity and machine has enough memory. We would recommend 500 URL per machine agent.

We would still recommend to spin up multiple machine agent rather than putting everything on one machine agent. I would recommend you to spin up one and test it performance one at a time. So in case of any issue we can work on it.

We have some problems with appdynamics, as the logs are errors related to the Product Database.

        Below are the errors found, and I would appreciate your support in solving the problems.


        Error 01 -
        170111 22:38:04 [Note] C:\AppDynamics\Controller\db\bin\mysqld.exe: ready for connections.
        Version: '5.5.46-enterprise-commercial-advanced-log' socket: '' port: 3388 MySQL Enterprise Server - Advanced Edition (Commercial)
        InnoDB: Error: tablespace id is 819019 in the data dictionary
        InnoDB: but in file .\controller\metricdata_ten_min#p#part205048#sp#part205048sp0.ibd it is 829506!
        170111 22:40:17 InnoDB: Assertion failure in thread 22464 in file fil0fil.c line 768
        InnoDB: We intentionally generate a memory trap.
        InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
        InnoDB: If you get repeated assertion failures or crashes, even
        InnoDB: immediately after the mysqld startup, there may be
        InnoDB: corruption in the InnoDB tablespace. Please refer to
        InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
        InnoDB: about forcing recovery.
       

        Error 02 -
        170111 22:32:49  InnoDB: cannot calculate statistics for table controller/requestdata_summary#p#part409607
        InnoDB: because the .ibd file is missing.  For help, please refer to
        InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
        170111 22:32:49 [ERROR] MySQL is trying to open a table handle but the .ibd file for table controller/requestdata_summary#p#part409607 does not exist.
        Have you deleted the .ibd file from the database directory under the MySQL datadir, or have you used DISCARD TABLESPACE?
        See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.htmlhow you can resolve the problem.


       Error 03 -
        170111 23:24:52  InnoDB: Error: table 'controller/eventdata_affected#p#part410194'
        InnoDB: in InnoDB data dictionary has tablespace id 834298,
        InnoDB: but a tablespace with that id does not exist. There is
        InnoDB: a tablespace of name .\controller\eventdata_affected#p#part410194.ibd and id 881526, though. Have
        InnoDB: you deleted or moved .ibd files?
        InnoDB: Please refer to
        InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
        InnoDB: for how to resolve the issue.



        Mode Details
        170111 22:38:04 [Note] C:\AppDynamics\Controller\db\bin\mysqld.exe: ready for connections.
        Version: '5.5.46-enterprise-commercial-advanced-log'  socket: ''  port: 3388  MySQL Enterprise Server - Advanced Edition (Commercial)
        InnoDB: Error: tablespace id is 819019 in the data dictionary
        InnoDB: but in file .\controller\metricdata_ten_min#p#part205048#sp#part205048sp0.ibd it is 829506!
        170111 22:40:17  InnoDB: Assertion failure in thread 22464 in file fil0fil.c line 768
        InnoDB: We intentionally generate a memory trap.
        InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
        InnoDB: If you get repeated assertion failures or crashes, even
        InnoDB: immediately after the mysqld startup, there may be
        InnoDB: corruption in the InnoDB tablespace. Please refer to
        InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
        InnoDB: about forcing recovery.
        170111 23:24:33 [Note] Plugin 'FEDERATED' is disabled.
        170111 23:24:33 InnoDB: The InnoDB memory heap is disabled
        170111 23:24:33 InnoDB: Mutexes and rw_locks use Windows interlocked functions
        170111 23:24:33 InnoDB: Compressed tables use zlib 1.2.3
        170111 23:24:33 InnoDB: Initializing buffer pool, size = 6.0G
        170111 23:24:34 InnoDB: Completed initialization of buffer pool
        170111 23:24:34 InnoDB: highest supported file format is Barracuda.
        InnoDB: Log scan progressed past the checkpoint lsn 34866073075
        170111 23:24:34  InnoDB: Database was not shut down normally!
        InnoDB: Starting crash recovery.
        InnoDB: Reading tablespace information from the .ibd files...
        170111 23:24:44 [Note] Plugin 'FEDERATED' is disabled.
        170111 23:24:44 InnoDB: The InnoDB memory heap is disabled
        170111 23:24:44 InnoDB: Mutexes and rw_locks use Windows interlocked functions
        170111 23:24:44 InnoDB: Compressed tables use zlib 1.2.3
        170111 23:24:44 InnoDB: Initializing buffer pool, size = 6.0G
        170111 23:24:44 InnoDB: Completed initialization of buffer pool
        170111 23:24:44 InnoDB: highest supported file format is Barracuda.
        InnoDB: Log scan progressed past the checkpoint lsn 34866073075
        170111 23:24:44  InnoDB: Database was not shut down normally!
        InnoDB: Starting crash recovery.
        InnoDB: Reading tablespace information from the .ibd files...
        InnoDB: Restoring possible half-written data pages from the doublewrite
        InnoDB: buffer...
        InnoDB: Doing recovery: scanned up to log sequence number 34866153163
        170111 23:24:51  InnoDB: Starting an apply batch of log records to the database...
        InnoDB: Progress in percents: 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55                 56 57 58 59 60 61 62 63 64 65 66 67 68 69                 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
        InnoDB: Apply batch completed
        170111 23:24:52  InnoDB: Error: table 'controller/eventdata_affected#p#part410194'
        InnoDB: in InnoDB data dictionary has tablespace id 834298,
        InnoDB: but a tablespace with that id does not exist. There is
        InnoDB: a tablespace of name .\controller\eventdata_affected#p#part410194.ibd and id 881526, though. Have
        InnoDB: you deleted or moved .ibd files?
        InnoDB: Please refer to
        InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
        InnoDB: for how to resolve the issue.

        Product Installed on Windows 2008
        Version - 4.2.0.2


Can you help us, please?

Hi Experts,

I am interested to export the data from "Scalability Analysis" tab for 'Applciation Load vs CPU" via API or any other mode.

Please guide me how to do so. [No Rest URL available I see]

Appreciate your quick help and response.

Regards,

Vaibhav

We have created Service Endpoints within transactions & the data collected is useful. We can now look back over the month & see the volume of calls to the various endpoints. This is really easy from the service endpoint screen but there is no way of exporting that data from that screen.

A possible workaround is to use the metric browser & select the endpoint data that way but that isn't ideal as you have to calculate the totals.

Have attached a picture.

Any ideas / thoughts would be greatly appreciated  

The Splunk integration is easy but the standard search it issues
(host=xxxxxxxx OR host=xx.xxx.xxx.xx OR host=xx.xxx.xxx.xxx)

Causes no results to be shown as our Splunk instance knows the server details under node= 

also all it has a port number so wildcards are required at the end of the details passed above.

The Extra Query Parameters are only appended so it can not be altered from there. Is it possible to amend the base search passed to splunk?? 

I found no docs of REST API metioned that how they support pagination (e.g. how can i get the next link from the reponse of API) after I reviewed all the rest api provided by appdynamics.

Does it mean that the REST API have no pagination? 

Hi,

I want to trial. After I installed Controller. When I tried to login, I got a error : 

"License file is not specified. Please drop the license file in the controller installation directory."

How to solve it ? 

I also didn't know how to get the license of on-Premises. Pls help. Thanks !

Attached is the screen shot of subscription of my account.  

Hi Team,

I wanted to know how can I set alerting for a specific BT where customer wants if there is no hit on that perticular BT in a span of 5 mins, there should be a critical alert triggered. They say one of the services call this service. So for them this service should be hitting all the time. If missed they want a trigger for the same.

Please suggest. Thanks.

Best Regards,

Saurabh

The Database Agent, from time to time (approximately 30 min), stops collecting the information. At this point it returns the following error (License (Expired, Limit Reached, Invalid File, Not Found)  ).

Below is more details at the time of the problem.

13 Jan 2017 13:26:05,135  INFO [<EP1>-Scheduler-2] ADBCollector:91 - DB collector 'EP1' shutted down!
13 Jan 2017 13:26:05,136  WARN [<EP1>-Scheduler-1] MetricSampler:117 - Can't report metric for status variable 'TotalCPU'
java.lang.NullPointerException at com.singularity.ee.agent.dbagent.model.sampler.factory.ASamplerFactor
y$ReusableMetricNameResolver.resolve(ASamplerFactory.java:38) at com.singularity.ee.agent.dbagent.model.sampler.MetricSampler.getMetri
cIdentifier(MetricSampler.java:72) at com.singularity.ee.agent.dbagent.model.sampler.MetricSampler.report(M
etricSampler.java:107) at com.singularity.ee.agent.dbagent.model.sampler.MetricSampler.report(M
etricSampler.java:89)  at com.singularity.ee.agent.dbagent.collector.server.AixCollector.collec
tCPUSamples(AixCollector.java:141) at com.singularity.ee.agent.dbagent.collector.server.AixCollector.collec
tSamples(AixCollector.java:131) at com.singularity.ee.agent.dbagent.collector.server.AixCollector.collec
t(AixCollector.java:113) at com.singularity.ee.agent.dbagent.collector.server.AServerCollector.ru
n(AServerCollector.java:164) at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutor
ServiceImpl$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)


13 Jan 2017 13:35:56,841  INFO [<EP1>-Scheduler-1] DBAgent:46 - Orchestration isdisabled - disabling one-way agent transport. The agent will not be able to execute workflow tasks.
13 Jan 2017 13:35:56,841  INFO [<EP1>-Scheduler-1] DBAgent:46 - Configuration manager successfully configured
13 Jan 2017 13:35:56,842  INFO [<EP1>-Scheduler-1] DBAgent:46 - Keystore file C:\dbagent-4.2.1\conf\cacerts.jks was not found
13 Jan 2017 13:35:56,843  INFO [<EP1>-Scheduler-1] DBAgent:46 - Started DB Collector Agent successfully
Started DB Collector Agent successfully
13 Jan 2017 13:35:57,838  INFO [<EP1>-Scheduler-2] ARelationalDBCollector:59 - (Re)initialize the DB collector 'EP1'.
13 Jan 2017 13:35:57,842  INFO [<EP1>-Monitor-Scheduler-1] DBCollectorAgentMonitorDelegate:76 - Starting transient session [[TransientEventData{sessionId='cde373f6-486e-4836-8a4f-b696ee0e535f', sessionType='DBMON', exceptionMessage='null',data=null, status='', operation='START_SESSION', nvp=[], nodeId=7, opId='d18cc34f-0ce5-44d8-b14a-93730806881c', transientBTSessionId='null', transientBTSessionOperationId='null'}
Agent Event Type[null]
Occurred at Time[0]
Summary[null]
Severity[null]
Event Details[{}]
Error IDs[[]]
Correlation Map[{}]
EventProperties[null]
]].
13 Jan 2017 13:35:57,843  INFO [<EP1>-Monitor-Scheduler-1] SystemAgentTransientEventChannel:230 - Received operation TransientEventData{ operation [START_SESSION], sessionId [cde373f6-486e-4836-8a4f-b696ee0e535f], opId [d18cc34f-0ce5-44d8-b14a-93730806881c], nvp = [[]]}
13 Jan 2017 13:35:57,844  INFO [<EP1>-Monitor-Scheduler-1] SystemAgentTransientEventChannel:46 - ########  Started the transient event channel ########
13 Jan 2017 13:35:57,847  INFO [<EP1>-Monitor-Scheduler-1] SystemAgentTransientEventChannel:46 - Started session for sessionID [cde373f6-486e-4836-8a4f-b696ee0e535f], sessionType [DBMON]
13 Jan 2017 13:35:57,858  INFO [<EP1>-Scheduler-1] SystemAgentTransientEventChannel:46 - Received [1] operations from controller.
13 Jan 2017 13:35:57,859  INFO [<EP1>-Scheduler-1] SystemAgentTransientEventChannel:46 - New operations arrived: [END_SESSION]
13 Jan 2017 13:35:57,860  INFO [<EP1>-Scheduler-1] SystemAgentTransientEventChannel:230 - Received operation TransientEventData{ operation [END_SESSION], sessionId [cde373f6-486e-4836-8a4f-b696ee0e535f], opId [null], nvp = [null]}
13 Jan 2017 13:35:57,860  INFO [<EP1>-Scheduler-1] SystemAgentTransientEventChannel:46 - Ended session for sessionID [cde373f6-486e-4836-8a4f-b696ee0e535f], sessionType [DBMON]
13 Jan 2017 13:35:57,860  INFO [<EP1>-Scheduler-1] SystemAgentTransientEventChannel:46 - No active sessions exist. The transient event channel will be terminated.
13 Jan 2017 13:35:57,861  INFO [<EP1>-Scheduler-1] SystemAgentTransientEventChannel:46 - ######### Stopped the transient event channel ########
13 Jan 2017 13:35:57,867  INFO [<EP1>-Scheduler-2] DB2Collector:67 - Full DB2 Version [9.7].
13 Jan 2017 13:36:12,055  INFO [<EP1>-Scheduler-2] AServerCollector:152 - (Re)initialize the hardware metric collector 'EP1'.
13 Jan 2017 13:36:12,057  INFO [<EP1>-Scheduler-2] SSHConnection:105 - Loading SSH key files from [C:\dbagent-4.2.1\keys]