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.
Is there any example of how to correctly call the AppDynamics rest API health rules using java?
Our team is working on calling the health rules API in appDynamics using java
( javax.ws.rs.client.Client.target library )
Below is the client request call put together, it is currently returning a socket timeout exception. From the research, I have done this should be the correct format in java on how to build the client call for the health rules, but is not working.
Wondering if someone from the community can provide more insight on how to do this in Java.
How do you build a java rest API client (javax.ws) to call the AppDynamics HealthRules API
import javax.ws.rs.client.Client; import javax.ws.rs.client.ClientBuilder; Client client = clientBuilder.build(); client.property(ClientConstants.METER_ID, "MyClientApp"); client.property(ClientConstants.SOCKET_TIMEOUT, 600000); client.property(ClientConstants.CONNECTION_TIMEOUT, 600000); client.property(ClientConstants.SECURITY_TYPE, 600000); client.property(ClientConstants.SECURITY_TYPE,SecurityType.BasicAuth); client.property(ClientConstants.USER_ID, "user@customer1"); client.property(ClientConstants.PASSWORD, "password"); healthRulesCall = client.target("https://appd-prod.mywork.com:8181/controller/healthrules/24").queryParam("count", 100) .queryParam("offset", 0).request().accept(MediaType.APPLICATION_XML_TYPE).get(String.class);
Socket timeout might be caused by not being able to connect through the network in between. Have you tried doing a telnet or curl to the following address ?
Also I saw you are using this property twice
Once with a number which might indicate a timeout and then with the actual authentication type. Maybe that needs to be fixed as well.
Anyways if there was something wrong with authentication then I would expect you receiving a 401 HTTP return code but it seems you are not even getting to your target.