@Andriy Knysh (Cloud Posse)
@Mitch this might help https://github.com/cloudposse/prometheus-to-cloudwatch#screenshots
Hey all, I’m looking to use https://github.com/cloudposse/prometheus-to-cloudwatch. Trying to figure out what my
cloudwatch_namespace is. Any advice on figuring it out?
My service is running in ECS with a FARGATE deployment
Hi all, anyone set up webpage client side metrics getting to Prometheus? I wanted to build a poc and I’ve found this https://www.weave.works/blog/browser-metrics-into-prometheus/. Does anyone have a different solution that would like to share, just to get some different options
@Gareth those docs are a bit out of date
I want to replace ELK stack that we use for log collecting in favour of Fluentd + CloudWatch. Now I can collect logs from customer application and kubernetes cluster to CW, also we use CW Container Insights as Kubernetes monitoring tools
We’re using this chart with success: https://hub.kubeapps.com/charts/incubator/fluentd-cloudwatch
Deploy the fluentd-cloudwatch v1.7.3-debian-cloudwatch-1.0 in Kubernetes. A Fluentd CloudWatch Helm chart for Kubernetes.
The only issue is restricting over-logging namespaces
hey Sergey, yes looks like lambda is the only way to go to move logs from S3 to CW
Good morning All, I’m looking for some advice around monitoring and wondered if somebody had the time to give me their opinions. I work for a company that’s got multiple AWS accounts, One company account (master) and then one per client which contain many VPC’s normal separated based on DEV, Test, Pre-Live and Prod per product we design. Primarily web sites or applications. We’ve historically used Cloudwatch and created the dashboards as an when we need something above and beyond the default EC2 monitoring but this is become costly and doesn’t really give us a centralised approach or the flexibility to add something that is beyond the basics. I’m looking to bring us in to a more centralised way of working and have been reviewing Prometheus + Grafana and maybe Thanos to get a more historical view of data. I’ve seen the SweetOps articles on Prometheus and read over the kubernetes example but I’m left confused as to what is the best way to architect a Prometheus platform. Most examples I’ve seen look to deploy Prometheus on kubernetes, but I would have thought it would be better off as an EC2 node. There also appears to be a split in the thinking that its would be best to deliver a Prometheus pair of server to each AWS account rather than trying to bridge from say the Companies Master account. Appreciate this is a wide and very generalized question but at this time any comments would be of help to me.