MENU
A system API that communicates to an underlying MySQL database is deploying to CloudHub. The DevOps team requires a readiness endpoint to monitor all system APIs.
Which strategy should be used to implement this endpoint?
30 comments · newest first
AM
Ammie
7 months ago
B is solid, but A gives a fuller picture. Can't go wrong with that!
RE
Renay
7 months ago
Option D is too limited. We need more than just API status.
BL
Blythe
7 months ago
I agree with A. We need comprehensive monitoring for reliability.
ON
Oneida
7 months ago
Option C seems too risky. Existing endpoints might not provide all needed info.
HA
Harrison
8 months ago
Definitely need to monitor server health too, so B makes sense.
LE
Lemuel
8 months ago
Surprised there's no mention of security for the endpoint!
TH
Thaddeus
8 months ago
Why not just use an existing resource? Seems simpler.
JE
Jeff
9 months ago
A dedicated endpoint for API status is crucial.
DI
Dierdre
9 months ago
Monitoring the API status and reachability is like checking the engine and fuel levels before a long road trip. Option A is the way to go.
JI
Jillian
9 months ago
Haha, using an existing resource endpoint? That's like trying to fit a square peg in a round hole. Option C is a no-go.
JU
Justine
9 months ago
Option B is a bit too limited. The DevOps team needs to know more than just the API status and server health.
RO
Ronnie
9 months ago
I agree with Krissy. Option A provides the most comprehensive information for the DevOps team to monitor the system's health.
KR
Krissy
9 months ago
Option A seems like the best choice to me. Monitoring the API status and reachability of the underlying systems is crucial for ensuring the system's reliability.
AM
Amalia
10 months ago
I recall a practice question where we had to choose between just status or status and health. I think option D might be too limited.
ED
Edda
10 months ago
I feel like using an existing resource endpoint might not give us the complete picture. Option C seems risky.
CR
Cristy
10 months ago
I'm not entirely sure, but I remember something about health checks being crucial. Could option B be the right one?
AL
Alpha
10 months ago
I'm leaning towards option A as well. Monitoring both the API status and the underlying systems sounds like the best way to ensure the system is truly ready for deployment.
CA
Carmen
10 months ago
Option C could be an interesting approach, but I'm worried it might not give the DevOps team all the information they need. A dedicated endpoint feels like the safer choice.
TR
Tresa
10 months ago
I think we discussed the importance of having a dedicated endpoint for monitoring, so maybe option A is the best choice?
GA
Gail
11 months ago
I prefer option B. Health of the server is crucial too.
KR
Kris
11 months ago
I think option A is the best. It covers both status and reachability.
JA
Jacqueline
11 months ago
I think option A is the best choice!
JU
Judy
11 months ago
Option D is just the tip of the iceberg. The DevOps team needs more details to effectively monitor the system.
FR
Franklyn
11 months ago
I'm a little unsure here. Option B seems simpler, just checking the API status and server health. But I'm not sure if that's enough for the DevOps team's requirements.
CH
Chaya
12 months ago
I think I'd go with option A. Creating a dedicated endpoint to monitor the API status and the underlying systems seems like the most comprehensive approach.
LA
Larue
6 months ago
Definitely A! We need that comprehensive view.
JO
Jonell
6 months ago
I like A as well, it covers all bases.
SH
Sharee
6 months ago
Option B could work too, but it’s not as thorough.
GL
Glennis
7 months ago
Yeah, monitoring both status and reachability is crucial.
TI
Timothy
7 months ago
I agree, option A sounds solid.