Splunk AppDynamics

credentials for using the controller API

CommunityUser
Splunk Employee
Splunk Employee

I am looking into using the controller API to get the reporting data out of my app. Following this link, using the command 

curl --user user1@customer1:secret http://demo.appdynamics.com/controller/rest/applications?output=JSON

what is user1, customer1 and secret here?

is user1 my username nahalam?

I think customer1 is the account name that starts with lee....

and secret is the access key I have in /etc/appdynamics.cfg file?

Using those, I get below error

curl: (6) Could not resolve host: demo.appdynamics.com

 

Please clarify.

Labels (3)
0 Karma
1 Solution

Atyuha_Pal
Contributor

Hi,

curl --user user1@customer1:secret http://demo.appdynamics.com/controller/rest/applications?output=JSON

user1-->username

customer1-->For a single-tenant Controller (which is the case for most on-premises Controllers), the account name should be the account name for the primary default account, which is "customer1".

If you are using a multi-tenant Controller (most SaaS Controllers), replace customer1 with your own, instance-specific account name. 

secret-->password

Example:

curl --user <your_username>@<your_accountname>:<your_password> http://<controller_host>:<controller_port>/controller/rest/applications?output-JSON
curl --user <your_username>@<your_accountname>:<your_password> http://<SaaS_url>/controller/rest/applications?output-JSON

Thanks,

Atyuha

View solution in original post

Atyuha_Pal
Contributor

Hi,

curl --user user1@customer1:secret http://demo.appdynamics.com/controller/rest/applications?output=JSON

user1-->username

customer1-->For a single-tenant Controller (which is the case for most on-premises Controllers), the account name should be the account name for the primary default account, which is "customer1".

If you are using a multi-tenant Controller (most SaaS Controllers), replace customer1 with your own, instance-specific account name. 

secret-->password

Example:

curl --user <your_username>@<your_accountname>:<your_password> http://<controller_host>:<controller_port>/controller/rest/applications?output-JSON
curl --user <your_username>@<your_accountname>:<your_password> http://<SaaS_url>/controller/rest/applications?output-JSON

Thanks,

Atyuha

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...