MENU
[Building and implementing service monitoring strategies]
Your organization is running multiple Google Kubernetes Engine (GKE) clusters in a project. You need to design a highly-available solution to collect and query both domain-specific workload metrics and GKE default metrics across all clusters, while minimizing operational overhead. What should you do?
Suggested Answer: C
Get Premium Professional Cloud DevOps Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
24 comments · newest first
GR
Gregoria
10 months ago
Wait, can managed collection really handle all that?
BR
Bronwyn
10 months ago
I agree, remote-write simplifies things a lot!
YO
Youlanda
11 months ago
I like option C for its simplicity and integration with Cloud Monitoring.
CH
Chandra
11 months ago
Option A is overkill, Thanos is not always necessary.
LA
Lauryn
11 months ago
I think option B is the best for centralizing metrics.
DE
Denise
11 months ago
I feel like using BigQuery for querying metrics could be overkill, but I’m not entirely sure how it compares to the other options.
EL
Elbert
11 months ago
I practiced a similar question where we had to choose between Prometheus and Cloud Monitoring, and I think Cloud Monitoring might be less operationally heavy.
VA
Valene
12 months ago
I think enabling managed collection sounds simpler, but I can't recall if it provides all the metrics we need.
KA
Karl
12 months ago
I remember discussing Prometheus and Thanos in class, but I'm not sure if I should go with the sidecar option or just use remote-write.
WI
Willie
1 year ago
I'm leaning towards option A with Prometheus and Thanos. It seems like the most comprehensive solution that would meet all the requirements, even if it might be a bit more complex to set up initially. The high availability and centralized querying capabilities are really important for this use case.
KA
Kayleigh
1 year ago
Option C looks tempting - using the managed collection in Cloud Monitoring could be a simpler solution. But I'm not sure if that would give me the same level of control and flexibility as running my own Prometheus setup. I'll have to weigh the trade-offs carefully.
IN
Ines
1 year ago
Hmm, I'm a bit unsure about this one. The question is asking for a "highly-available" solution, and I'm not sure if the remote-write approach in option B would be as robust as the Thanos setup in option A. I'll need to think this through carefully.
LI
Ling
1 year ago
This looks like a pretty straightforward question on monitoring strategies for GKE clusters. I think I'll go with option A - using Prometheus Operator and Thanos to set up a centralized monitoring solution. Thanos should give me the high availability and querying capabilities I need across all the clusters.
RE
Reita
1 year ago
I agree with Daron, using Prometheus Operator with Thanos sidecar seems like a good solution.
SH
Shawna
1 year ago
Remote-write to Prometheus? That's like the monitoring equivalent of copy-pasting code from StackOverflow. Gotta love it!
LI
Lina
1 year ago
Prometheus and Thanos, huh? Reminds me of the old days when we had to build our own monitoring stack from scratch. Ah, the good old days!
DE
Deangelo
1 year ago
BigQuery, eh? Interesting choice, but I'm not sure how well it would handle real-time metric queries.
LE
Leigha
1 year ago
Managed collection in Cloud Monitoring? Sounds convenient, but I wonder how much control we'd have.
DA
Daron
1 year ago
I think option A is the best choice.
CO
Cory
1 year ago
Remote-write to a central Prometheus? Nice and simple, I like it.
MA
Martha
1 year ago
Prometheus Operator with Thanos? Sounds like a lot of moving parts, but I guess it's the most flexible solution.
MA
Marti
1 year ago
A) Prometheus Operator with Thanos can be complex, but it offers flexibility.
LO
Loren
1 year ago
B) Use Prometheus Operator to install Prometheus in every cluster and scrape the metrics. Configure remote-write to one central Prometheus. Query the central Prometheus instance.
LO
Louann
1 year ago
A) Use Prometheus Operator to install Prometheus in every cluster and scrape the metrics. Ensure that a Thanos sidecar is enabled on every Prometheus instance. Configure Thanos in the central cluster. Query the central Thanos instance.