MENU
What are three valid reasons to use the AppDynamics REST API to retrieve metrics? (Choose three.)
Suggested Answer: A, C, E
Get Premium 500-430 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
To archive 1-minute granularity data. The AppDynamics Controller stores metric data at different levels of granularity depending on the retention period. For example, it stores 1-minute granularity data for 8 days, 10-minute granularity data for 32 days, and 1-hour granularity data for 365 days. If you want to archive the 1-minute granularity data for longer than 8 days, you can use the API to retrieve and store the data in an external database or file system.
To calculate a new metric based on two existing metrics. The AppDynamics Controller provides some built-in metrics such as average response time, calls per minute, errors per minute, etc. However, you may want to calculate a new metric that is not available in the Controller, such as the ratio of errors to calls, or the percentage of slow transactions. You can use the API to retrieve the values of the existing metrics and perform the calculation using your own logic or formula.
32 comments · newest first
RE
Rex
11 months ago
Wait, can you really use the API for health rule violations? That's surprising!
WI
Wilbert
11 months ago
D? Not sure if that's a valid reason, seems a bit off.
MA
Maybelle
11 months ago
C makes sense, calculating new metrics can provide deeper insights.
CA
Cary
11 months ago
I think B is a solid choice too, custom reports are super useful.
RH
Rhea
12 months ago
A is definitely a reason, 1-minute granularity is crucial!
BE
Bev
12 months ago
I’m a bit confused about the health rules part. I think evaluating health rules might be relevant, but I can't recall if that's option D or something else.
VA
Vanna
1 year ago
I feel like calculating new metrics based on existing ones could be useful too, like option C. We discussed that in the last review.
CH
Christiane
1 year ago
I'm not entirely sure about all the options, but I remember something about retrieving health rule violations being important for monitoring. Maybe option E?
DO
Dominque
1 year ago
I think using the API to create custom reports is definitely a valid reason, like option B. That sounds familiar from our practice sessions.
FR
Francesco
1 year ago
I think I've got it figured out. The key is to identify the options that allow you to extend the functionality of AppDynamics beyond the standard reporting and alerting capabilities. That's where the real value of the API comes in.
JO
Jose
1 year ago
I'm a bit confused by some of these options. Evaluating health rules and retrieving health rule violations - are those really valid reasons to use the API? I'll need to double-check the documentation on that.
CL
Clement
1 year ago
Okay, I've got a strategy here. I'll focus on the key use cases like archiving data, creating custom reports, and calculating new metrics. Those seem like the most relevant reasons to use the API.
CL
Clay
1 year ago
Hmm, I'm not too familiar with the AppDynamics API, so I'll need to think this through carefully. Let me review the options and see which ones make the most sense.
MA
Margarita
1 year ago
This looks like a straightforward question about the AppDynamics REST API. I should be able to handle this.
AL
Alva
2 years ago
Haha, gotta love these API questions. I'm going with C, E, and F - can't go wrong with custom metrics, health rule violations, and internal alerts!
KR
Krissy
2 years ago
Definitely, those are all valid reasons to use the AppDynamics REST API.
IN
In
2 years ago
Creating alerts for internal ticketing systems is a must.
QU
Queenie
2 years ago
I agree, health rule violations are important to monitor.
MA
Margart
2 years ago
Samesies! Custom metrics are always useful.
MA
Marge
2 years ago
This is a tricky one, but I think D, E, and F are the way to go. The API is great for getting a deeper look at your application's health and performance.
GE
Georgiana
2 years ago
I believe option F is important too, creating alerts for internal ticketing system.
IS
Isadora
2 years ago
Hmm, I'm not sure about B. Isn't that more of a use case for the standard AppDynamics dashboard? I'd go with A, C, and F.
FE
Felicitas
2 years ago
Yes, evaluating health rules could definitely be another valid reason to use the API.
LA
Latricia
2 years ago
But what about evaluating health rules? Wouldn't that be important too?
DE
Deeanna
2 years ago
I agree with you, A, C, and F seem like more common reasons to use the API.
EL
Elise
2 years ago
I think B could still be valid for creating a custom report.
HE
Herschel
2 years ago
I agree with you, Loren. Option B also seems useful for creating custom reports.
VI
Viki
2 years ago
A, C, and E are definitely the right choices here. Retrieving metrics with the AppDynamics REST API is super useful for all sorts of custom reporting and analysis needs.
FI
Fidelia
2 years ago
User 3: It's great that you can calculate new metrics based on existing ones.
JU
Julio
2 years ago
User 2: I agree, using the API for custom reporting is very helpful.
GO
Goldie
2 years ago
A, C, and E are definitely the right choices.
LO
Loren
2 years ago
I think option A is valid because archiving data is important.