![]() Reading correctly) should be the same, but it is, at least for us, pretty slow. Terms of GetMetricStatistics instead of GetMetricData. ![]() Make it fire, but I intend to experiment and bounce ideas off coworkers.Īs a side note I think it’s important to mention that the officialĬloudwatch-exporter has some performance issues due to being implemented in I’m not thrilled with the above, since a huge spike in inbound messages could Here’s a sample of the exported metrics above: aws_sqs_approximate_age_of_oldest_message_maximum) > 0 I looked over the list and our notes from a meeting on how we should monitor SQSĪnd came up with the following configuration for cloudwatch-exporter:Īws_metric_name: ApproximateAgeOfOldestMessageĪws_metric_name: NumberOfMessagesReceivedĪws_metric_name: ApproximateNumberOfMessagesVisible The first AWS service I wanted to add monitoring on is SQS SQS is AWS’ queue This is a little abstract, but I’ll explain it more as we go. $0.01/1,000 metrics requested using GetMetricData First off, a quickĭoing a bunch of GetMetricData requests, and these requests end up querying some ![]() So that teams can monitor and alert on their infrastructure. ![]() I am writing up a bunch of initial configuration for our cloudwatch-exporter Tell, exposes all the various bits we could ever want. The most part, cloudwatch-exporter works perfectly well and, as far as I can If you use AWS and want to monitor your infrastructure, you probably are going Today I spent a few hours figuring out how to integrate Prometheus with AWS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |