Discussion Feed

Lyubo.Dimitrov · ‎08-04-2020

Hi Mario, Thanks for your comment, I had another look on the UI, inspecting the requests through the developer console and what I found is that on LITE account, on the Metric Browser page the Custom time range is not available. So the queries are only with BEFORE_NOW time range type. If I check the same on a PRO instance, I have the Custom time frame on the UI and the request on the background is actually using BETWEEN_TIMES parameter. So I tend to agree that the BETWEEN_TIMES parameter is actually not allowed for LITE version, though it is not clearly stated... It would make much more sense to either get a more descriptive error from the API or at least note it in the documentation. And just to comment, the use case I need the start/end time for is an integration. So using the start/end parameters on scheduled queries is the best way from integration perspective. Using the last n could cause either performance issues or gaps in the data. Another thing I noticed by inspecting the network requests is that the frontend is using a match better API request for retrieving the metrics data 🙂 which would be really good if exposed in documentation and supported. THanks, Lyubo

Lyubo.Dimitrov · ‎08-03-2020

Hey guys, Recently I found an issue when using the AppDynamics API to retrieve metrics or events on a LITE account. I know about the restriction on the last 1440 minutes and I comply with it by requesting data for less that. However the API still returns the 400 error with body: "HTTP Status 400 - For LITE Account only last 1440 minutes of data could be extracted" It is weird because I request less than the limit, for example the request that I use is: GET /controller/rest/applications/9077/metric-data?output=JSON&metric-path=Overall+Application+Performance%7C*&time-range-type=BETWEEN_TIMES&start-time=1596446430281&end-time=1596446434281&rollup=false HTTP/1.1 The time range defined between the start-time and end-time parameters is only a few seconds and it is just a minute in the past relative to the time of initiating the request, so it fits in the limit of last 1440 minutes, however I still have the error... If I try to request data using the BEFORE_NOW parameter, like: GET /controller/rest/applications/9077/metric-data?output=JSON&metric-path=Overall+Application+Performance%7C*&time-range-type=BEFORE_NOW&duration-in-mins=10&rollup=false HTTP/1.1 I get successful response. BUT I don't see anywhere on the documentation that the I did look on the documentation and I don't BETWEEN_TIMES time range type is not supported on LITE accounts. So bottom line the questions is why the BETWEEN_TIMES range type does not work on my LITE account?

Lyubo.Dimitrov · ‎07-31-2020

Hey Mario, What do you mean by 'Server'? Is it the AWS EC2 instance? I did check my EC2 instance which I am testing with and I don't have any tags there... Then I manually added a tag called 'resource-id' and entered the actual instance id: and now I can see the AWS|resource-id tag in AppDynamics: So, does this mean that AppDynamics Tags on the AWS server are only the tags which are actually available on the EC2 instance in AWS? And does it mean that this AWS|resource-id must be added somehow on the EC2 instance by the users in order for it to be visible in AppDynamics?

Lyubo.Dimitrov · ‎07-30-2020

Just to add that I already added a role to the EC2 instance as described in the documentation but it didn't make a change. Also I am using AppDynamics cloud so I don't have access to ' Configuration Options for Server Tagging' but I believe default values are in place for my instance now.

Lyubo.Dimitrov · ‎07-30-2020

Hello, I have app and machine agents deployed on an Ubuntu EC2 instance and they are both successfully connected to AppDynamics. The AppDynamics Server has the SIM enabled and is successfully correlation to the APM application. The problem is that when I go to the details view of the Server and scroll to the bottom I can see some AWS tags like: AWS|instance-type AWS|ami-id AWS|region AWS|security-group AWS|availability-zone however I am missing the AWS|resource-id tag which is listed in the documentation on the table under ' Amazon Web Services ': https://docs.appdynamics.com/display/PRO45/Server+Tagging How can I get the resource-id displayed in AppDynamics?

Lyubo.Dimitrov · ‎07-06-2020

Hey Mario, That's perfect! Thanks a lot! Is this API available on some documentation? I couldn't find it anywhere... Also, are there any other APIs available which are not described here: https://docs.appdynamics.com/display/PRO45/AppDynamics+APIs

Lyubo.Dimitrov · ‎07-06-2020

Is it possible to get the TAG data of a server from the AppDynamcis API? I have a Machine Agent installed on an ubuntu hosted on AWS and from the AppDynamics > Servers > Dashboard I can see a pane with "Tags", i.e.: AWS|Instance-Type AWS|region AWS|ami-id etc.. I am looking for a way to extract this information from the AppDynamics API.

Date Registered	‎07-06-2020 04:48 AM
Date Last Visited	‎08-07-2020 12:39 AM
Total Messages Posted	7
Total Kudos Received	1

Discussion Feed

Re: API 400 error when using BETWEEN_TIMES paramet...

API 400 error when using BETWEEN_TIMES parameter o...

Re: AWS resource-id tag is not available

Re: AWS resource-id tag is not available

AWS resource-id tag is not available

Re: Extract Server Tags from API

Extract Server Tags from API