Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
LogicMonitor’s AWS DataSources rely on the CloudWatch API to get data for your AWS resources. AWS offers 1 million free CloudWatch API requests per month, however; API requests beyond that free tier cost $.01/1000 requests. Depending on which AWS services you are monitoring and how many resources you are monitoring, you may see CloudWatch costs associated with LogicMonitor’s AWS Monitoring.
In addition to estimating them, this article focuses on the following three approaches to reduce CloudWatch spend:
Yes – You can estimate the CloudWatch costs if you understand the details around how LogicMonitor makes requests to the CloudWatch API and reference AWS’s published CloudWatch Pricing page.
LogicMonitor makes one CloudWatch API request to the GetMetricStatistics resource per normal datapoint collected, per polling interval of the DataSource. The reason behind this approach is that AWS restricts requests to this API resource to be per metric. Because we want to make sure you get as close as possible to real-time alert evaluation, most of our CloudWatchDataSources poll every 1 – 5 minutes, depending on how often CloudWatch metrics are published for the service in question.
As previously stated, AWS offers 1 million free CloudWatch API requests per month, and charges $.01/1000 requests beyond that. That means, if you surpass the free tier, you can essentially consider it to be $10 off your monthly CloudWatch bill. If you are using the default CloudWatch DataSources, you can estimate the costs per resource per month by multiplying the number of datapoints by the number of times each datapoint will be polled per month (according to the polling interval) and multiplying that by the 1 cent per 1000 API calls rate. This estimate will vary from service to service based on the associated Datasource’s polling interval and the number of datapoints. Here are a few examples of what the calculation looks like:
As a best practice, we recommend reading the section below to optimize your CloudWatch costs.
There are several ways to make sure your CloudWatch costs remain at a manageable level:
In This Article