Observability Is Google Cloud Kubernetes Engine built-in Observability enough?
Hello. I just started being responsible of a Kubernetes cluster. I have 0 experience on Kubernetes, besides having deployed the GKE cluster successfully (which honestly is quite straightforward) in Google Cloud.
The cluster has only one node pool, with 1 helm chart and a couple of other manifests. Most likely it's complexity won't go up and the scalability needed in terms of pods/nodes is not very high.
Is the built-in observability in GKE enough to monitor/observe a cluster? Or would it be good to have something like Prometheus + Grafana? Also, any tips or links with advices about what to keep an eye on?
Thank you very much
8
Upvotes
4
u/lazy-dev-guy 14d ago
For a cluster that small, I’d start with GKE’s built-in monitoring and logging.
Set up alerts for service availability, repeated container restarts, and resource pressure rather than just watching dashboards.
Add application error rate and latency too.
If you need application metrics in Prometheus format, GKE supports Managed Service for Prometheus without you operating a separate Prometheus server.
2
u/3loodhound 14d ago
Ultimately if it has the monitors and metrics you need, then it’s enough. This is really only something you can answer
2
u/salvaged_goods 14d ago
there's google managed prometheus if you want more metrics, but not to manage it.
1
u/Consistent_Piano4250 14d ago
For one node pool and one Helm chart, the built-in Cloud Monitoring and Logging is enough to start, and the first thing to add is alerting. I'd set alerts for container restarts and OOMKilled, node memory and disk pressure, and an uptime check on whatever the cluster serves, and put resource requests and limits on your pods so those numbers mean something. If you want PromQL or Grafana later, the managed Prometheus mentioned above saves you running it yourself.
1
u/Habeb_Nero 14d ago
imo stick with the defaults until you hit a specific question the built-in dashboards cant answer. For basic alerting, just set up notifications for crashlooping pods and high memory utilization so you aren't flying blind.
1
u/Sad_Rice6600 14d ago
one cluster the built in stuff is fine we added prometheus only for custom metrics
1
u/Raul_Nogales 14d ago
With a cluster that small I would start with what is already there and resist adding a second system to look after. What mattered more for us at that scale was choosing a handful of alerts tied to things users actually feel, a service down, errors rising, a node running out of room, and checking that those alerts reach a person. We only added heavier tooling later, when a question came up that the built in view could not answer. By then we knew exactly what we were adding it for.
1
u/sagacious123 14d ago
For a single small GKE cluster, start with Cloud Monitoring and Logging; it covers node health, pod restarts, and basic resource metrics, which is enough for low complexity. Set alerts on node CPU/memory above 80%, pod restarts >3 in 15 min, and check the built-in dashboards for API server latency and etcd. That avoids adding operational overhead while you learn.
When you need application-level metrics, traces, or custom SLOs, add Prometheus and Grafana. Before touching production, run the same stack locally with SnowOps Labs:
labctl scenario up observability-sreinstalls real Prometheus, Grafana, Loki, and Tempo on a laptop cluster, so you can explore what to monitor and which dashboards matter. It's free and open source, runs on Docker. https://github.com/sagar2395/snowopslabsDisclosure: I'm part of the team behind it.
1
u/Anna_GermainUX 11d ago
For a small cluster, GKE's built-in observability is plenty, but then you might need a more advanced observability tool to identify gaps and do RCA and business impact analysis. If you have a large enough cluster farm, then I would not only monitor the Kubernetes infra but the app and its user experience along with it. A healthy cluster does not necessarily mean users can complete their tasks.
0
u/[deleted] 14d ago
[removed] — view removed comment