Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
I am trying to connect to an IBM Data Power server using the Appdynamics extension. However, I am getting an authentication failure when trying to connect to DP. The reason for the failure is that the request originating from the AppDyanmics monitor does not have a certificate in it. I tried finding any documentation regarding SSL set up for Data power monitors but unable to find any.
Can someone please guide me on how this can be configured?
Thanks for posting the query on the AppDynamics Community.
We are unable to locate the extension (IBM Data Power) you are referring to in the list of extensions listed in AppDynamics Exchange. To investigate further, request you to share exact name of the AppDynamics extension that you are using.
Please add the following fields to your config.yml file.
Under the server you are trying to monitor, add the following field for SSL.
servers: - uri: http://localhost:5550/service/mgmt/current displayName: server1 username: user password: welcome useSsl: true
sslTrustStorePath: "" # If not set, defaulted to machine-agent/conf/extensions-cacerts.jks. The prop "-Dappdynamics.extensions.truststore.path=/path/cacerts" takes precedence if set
Do let us know if you face any further issues.
I tried adding the parameters to the file, but it does not look like the certificate is getting picked up. Do we have a way to determine from the logs the certificate which is being sent across ?
Below is the snapshot of the config.yml file, not sure if there is something which I might be missing. Can you please check if this looks fine to you or if there are any changes which needs to be made?
#This will create it in specific Tier. Replace <TIER_NAME>
metricPrefix: Server|Component:XXX-XXX|Custom Metrics|DataPower
- uri: https://xxxxxxxxxxx:5550/service/mgmt/current
- uri: https://XXXXX:5550/service/mgmt/current
# - uri: https://someotherhost:5550/service/mgmt/current
# displayName: server2
# username: user
# passwordEncrypted: C043Fag+LKEZM0AQTWPy2g==
# - fin_domain.*
# - .*security.*
# useBulkApi: true
# number of concurrent tasks
Please file a support ticket and attach the /logs, /conf and the /monitors folder for us to further investigate this issue.