I'm trying to wrap my head around the fact that we still need our own prometheus server with AMP... AMP supposedly allows for easy scalability and provision of resources, but then I need to handle the Prometheus server anyway. So why should I use it? It's a legit question, I don't get it and I wanted a simple solution to monitor my services running on EC2/Beanstalk. But it looks like I could be better off not using AMP.
There is a new feature called managed collector. At the moment it can only collect metrics from EKS but if that's your use case you might be covered :), see aws.amazon.com/about-aws/whats-new/2023/11/amazon-managed-service-prometheus-agentless-collector-metrics-eks/
@@cloudonaut Thanks a lot for the reply, your content is superb! I'm looking forward to digging more into your videos, they're helping me a lot. I'm not using EKS, and a lot of the documentation for AMP seems directed to it. My idea is that I'm gonna try pushing my metrics directly to AMP using the write endpoint, using the prometheus-client library for Python. I'm not confident it will work, but I'll see. If you have any pointers you could give me, I would appreciate. thanks!
Hi, I have one question when we say that AMP provides high scalability can this not be achieved if we create a self managed Prometheus as daemon set that would scale itself depending upon the nodes it has to monitor ?
Not sure if this is the right place to ask but here I go: This was posted 3 months ago so I believe things were changed since then, but one thing I still cannot understand, and that is why does the deployment comes with prometheus-for-amp-alertmanager disabled, and what would be the benefit of enabling it, and how do I configure it most importantly?? I have configured the prometheus-for-amp-server to use the AWS workspaces endpoint. Does that substitutes the usage of the amp-alertmanager?
Great video and sound quality! Can see that huge effort has been invested for all your videos, have subscribed to your channel! 😀
Thank you!
Another great video, thank you for doing this :)
Thanks a lot for your feedback!
Adding info about Thanos and Cortex implementation of Prometheus will help in bridging info gap between regular Prometheus vs amp
Thanks for bringing that up, @AdalarasuRS.
I'm trying to wrap my head around the fact that we still need our own prometheus server with AMP... AMP supposedly allows for easy scalability and provision of resources, but then I need to handle the Prometheus server anyway. So why should I use it? It's a legit question, I don't get it and I wanted a simple solution to monitor my services running on EC2/Beanstalk. But it looks like I could be better off not using AMP.
There is a new feature called managed collector. At the moment it can only collect metrics from EKS but if that's your use case you might be covered :), see aws.amazon.com/about-aws/whats-new/2023/11/amazon-managed-service-prometheus-agentless-collector-metrics-eks/
@@cloudonaut Thanks a lot for the reply, your content is superb! I'm looking forward to digging more into your videos, they're helping me a lot. I'm not using EKS, and a lot of the documentation for AMP seems directed to it. My idea is that I'm gonna try pushing my metrics directly to AMP using the write endpoint, using the prometheus-client library for Python. I'm not confident it will work, but I'll see. If you have any pointers you could give me, I would appreciate. thanks!
@@angelotessaro Good luck :)
Hi, I have one question when we say that AMP provides high scalability can this not be achieved if we create a self managed Prometheus as daemon set that would scale itself depending upon the nodes it has to monitor ?
Hi! Sorry, we have no experience scaling Prometheus.
Not sure if this is the right place to ask but here I go: This was posted 3 months ago so I believe things were changed since then, but one thing I still cannot understand, and that is why does the deployment comes with prometheus-for-amp-alertmanager disabled, and what would be the benefit of enabling it, and how do I configure it most importantly??
I have configured the prometheus-for-amp-server to use the AWS workspaces endpoint. Does that substitutes the usage of the amp-alertmanager?
Yes, alert manager was added ~ one month ago, see aws.amazon.com/blogs/mt/amazon-managed-service-for-prometheus-is-now-generally-available/
@@cloudonaut wow thanks a milion for the clarification, I was bashing my head over and over to understand it! Respect! :)
Amazing video. One of a kind on this topic atm - If I am correct. Thank you 🙏
Thank you for your feedback!
what is the main difference between AMP and Chronosphere ?
I don't know. Have not heard about Chronosphere before.