A prospect of ours is evaluating AppDynamics Pro 3.8 and AppDynamics for Databases 2.8. The integration is failing with a StringIndexOutOfBoundsException rather than displaying the list of possible database choices. I have tried to add some mappings by hand but it has made no difference. See the screenshot attached.
Regards,
Martin.
Hi Martin,
Apologies for delay in response. We suspect this could be a bug we would like go through the logs once to see any specific errors if any and based on the analysis we are planning to get in touch with our AppD4DB product expect regarding as we we have not encountered this error earlier in other customer environments:
Can you please send the following logs for intial analysis :
- Complete screenshot from /controller UI with backend dashboard and backend properties in view, from which you try to drill down from controller UI to dbtuna UI
- Screenshot from agents list in AppD4db UI
- Entire <ad4db>/apache-tomcat/logs folder zipped
- Entire <ad4db>/agent/logs folder zipped
Regards,
Arun
Hi Arun,
Mysteriously it has stopped reporting the error, possibly following the addition of two more database instances.
Some follow-up questions.
Regards,
Martin.
Hi Martin,
Glad to hear that news from you. Please find our response to your queries inline:
>>>>>> I undertand that the ability to map to an individual statement when you click the link is on the roadmap for SQL Server. Is this correct?
Answer: Are you referring to the case "when user is in the flow map instance a user should be able to launch AppD4DB and see only queries that were part of the snapshot" if this is the case yes it is in roadmap, let us know if any disconnect in our understanding.
>>>>>> The ADO connection string points to an individual database within the SQL Server instance. Is there anyway to map to the correct database. Is this also on the roadmap?
Answer: We have some bug fixes around this sql server for dot .net backend we see such issues when the backend properties in dashboard of controller UI does not match with ad4db agents list, check if info in doc link helps here:
http://docs.appdynamics.com/display/ADDB/Manually+Map+a+Database
Regards,
Arun
Hi Arun,
Yes, that is what I meant by my first question - thanks.
Regarding the second question, if you look at the two manual mappings that I defined, the ADO connection strings refer to the same SQL Server instance but different target database (SK v MO). There doesn't seem to be any way to differentiate - they get mapped to the same AppD instance. Ideally, you could extend the mapping definition to include more context such as the database.
Regards,
Martin.
Hi Arun,
The error is back! Some more logs this time. Not sure you can clearly make out the ADO connection string from the screenshot but it is in the manual mapping section that I defined - H3CTCQA0031-GFN_SHELL_SK_OLTP.
Regards,
Martin.
Hi Martin,
Can you help us check to debug as follows:
- check whether datasource is in sync with collector we do not see any collection with following details?
Host=H3CTCQA0031
Database=GFN_SHELL_SK_OLTP
as stated in docs http://docs.appdynamics.com/display/ADDB/Manually+Map+a+Database
Can you check backend properties in UI and check with collector is in sync with the above listed doc, if that does we request you to raise a ticket at help.appdynamics.com or email to help@appdynamics.com so that we will involve our product export on this issue.
Regards,
Arun
Hi Arun,
The above data source should map to GFN_Database on host h3ctcqa0031, which is in the screenshot of the collectors.
Regards,
Martin.
Hi Martin,
We would like to escalate the stringindex error issue, Can you help us in filing a request at https://help.appdynamics.com/tickets/new or send email to help@appdynamics.com ? . As we stated earlier we would like to involve our product expert in help ticket to find the root cause of the issue
Regards,
Arun