Discussion Feed

Hi   Availability is relative and would be different in every organisation.   You need to define what you would classify as you availability metrics for an Application and use the Appdynamics metrics to calculate this.   As an example for 1 Application you might have 6 nodes load balanced handling traffic, and 1 of them goes offline, however all other traffic is routed and handled without any problems. thereby producing no errors and users were not affected.   Would you classify the Application as 100% available, due to no errors and users affected, even though one node went offline. or would the one node being down affect your availability.   Ciao     ... View more

Hi guys   Elasticsearch is not supported OOB   You can use the following as a starting point Create a POJO Rule as follows   Class - org.elasticsearch.rest.RestController Method - dispatchRequest   Split Transactions using - Parameter o Getter Chain - path()   This will give you Transactions being detected   Please then also add the following package org.elasticsearch.* class to call graphs as without it you would only see the entry points   For additional data, you can enable the "find entry points" node property and then using the Business Transaction logs look to find more entry points if needed   Ciao ... View more

Hi there   It should be as follows   Default configuration for the AppDynamics plugin only needs the following information to connect to the AppDynamics REST api: REST uri: The uri where AppDynamics Controller is living. Same uri as you would use for logging into the AppDynamics dashboard.        Example : https://controller1.saas.appdynamics.com/controller   Username: Username for authentication. Don't forget the "@<domain>" part if using a multi-tenant Controller.      Example below       If you use a Multitenant environment - user1@account       If you use single tenant environment - user1     Password: Password for authentication.        Password for your user that you created with Read access to the API   Application Name: Name of the application that should be monitored, exactly as it appears in the Controller (possibly with spaces). Also accepts the application id (numeric value). ... View more

Hi Bill   Most likely it's just a typo.   The latest version you can view from the Appdynamics downloads is 20.7 Just use 20.7 instead of 20.8 and continue with the installation   Ciao ... View more

Thanks   Ok first step is to understand how the InfoBIP API needs your request to be formatted.   I cant get the exact details from the docs   Also I am not sure if the payload has an issue but you have the "to" section end with a } { "from":"abc@xyz.com", "to":"test@xyz.com}", "subject":"AppDynamics", "text":"Appdynamics test Event" }   Assuming the correct payload should be as below { "from":"abc@xyz.com", "to":"test@xyz.com", "subject":"AppDynamics", "text":"Appdynamics test Event" }   Can you test  ... View more

Hi There   I am assuming you have validated the same using Postman/SOAP UI? and it's working? Have you added the 2 headers below to the setup in AppDynamics to the request   Accept: application/json Content-Type: application/json   Let me know   Ciao ... View more

Hi There   For Sending Health rule events, you can use the normal kafka REST API Example below of a post request, which you can convert into a http request template.   curl -X POST -H "Content-Type: application/vnd.kafka.json.v1+json" \ --data '{"records":[{"value":{"foo":"bar"}}]}' "http://localhost:8082/topics/test" {"offsets":[{"partition":0,"offset":0,"error_code":null,"error":null}],"key_schema_id":null,"value_schema_id":null} ... View more