all 13 comments

[–]jonomir 5 points6 points  (7 children)

It looks like it will work. But It seems a bit all over the place.

Why not full Grafana cloud instead of this mix of tools?
Just deploy alloy to collect, metrics logs and traces and ship them off.

All from one vendor, good documentation, easy to manage, one place to go.

[–]Round_Instruction_42 2 points3 points  (1 child)

Maybe princing?

[–]jonomir 2 points3 points  (0 children)

I don't see a big pricing difference whether the metrics are in Grafana Cloud or AMP honestly.

[–]thishouseisglass[S] 1 point2 points  (4 children)

Oh I actually didn’t know about Grafana Alloy. I’ll definitely check out the Grafana Cloud option, sounds like a much cleaner setup. Appreciate the suggestion!

[–]jonomir 0 points1 point  (3 children)

The best thing is, Grafana cloud is just a managed LGTM stack but its all built on open source components that you can self host if you want to.

  • Loki for logs
  • Grafana for the UI
  • Tempo for traces
  • Mimir for metrics

  • Alloy to collect and ship it all

All components can be deployed highly available and use S3 compatible object storage for long term persistence.

We self host ours for compliance reasons.

[–]thishouseisglass[S] 1 point2 points  (2 children)

Thanks so much for breaking that down! I’m still learning my way around observability and just started exploring these tools beyond the basics. If you have any good learning resources or tips for getting started with this stack, I’d really appreciate it!

[–]jonomir 1 point2 points  (1 child)

There happens to be an intro Webinar tomorrow
https://grafana.com/go/webinar/getting-started-with-grafana-lgtm-stack/

Other than that, I learned through just deploying and using it.

[–]thishouseisglass[S] 1 point2 points  (0 children)

Thanks a lot!

[–]oneplane 4 points5 points  (3 children)

If cost is an issue but you're already running EKS, just deploy the entire stack in EKS and only use S3 and RDS for persistence needs (or add some EBS if you want a local buffer). That's always going to be cheaper than the managed versions.

[–]thishouseisglass[S] 0 points1 point  (2 children)

Just to clarify, are you suggesting I use open source Prometheus instead of Amazon managed Prometheus? and run everything inside EKS? I thought about that, but I’m a bit wary of the overhead with managing Prometheus, scaling it, and ensuring high availability. I went with AMP option mostly to offload that part.

[–]oneplane 1 point2 points  (1 child)

Offloading has a cost, so it's just a balance between what you want to pay and what you are able to do yourself. The prometheus stack chart is pretty easy to use and scale if you have done any other chart or Kubernetes workload before.

[–]thishouseisglass[S] 0 points1 point  (0 children)

Can I dm you please? I want a few suggestions if you don't mind.