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 currently supports monitoring of billing data via AWS Cost and Usage Reports.
To get started, you’ll need to perform the following steps:
LogicMonitor can monitor the cost of any line items in your Cost & Usage Report. We have five out-of-the-box DataSources (listed below), but custom DataSources can be used to extend what is monitored. Pre-configured DataSources include:
From your AWS console, navigate to your username in the upper right corner and select ‘My Billing Dashboard’.
Next, click “Cost & Usage Reports” on the left. Next, create a report with the following configurations:
Make sure you enable support for Redshift – this does not actually require that you run any Redshift instances, but will include a script with the saved billing file that LogicMonitor uses to format and process the data.
The resulting configuration should look like this:
You’ll also need to configure an S3 bucket on the next page, and specify a report path. Remember the path and bucket specified, as you’ll need to provide them in LogicMonitor later. Note that the S3 bucket you specify will need to include permission for the Cost & Usage Reports to be saved. You can use the sample policy provided by AWS (confirm bucket name) and the policy can be added to your bucket on the Permissions tab for the bucket.
Your LogicMonitor role needs to have sufficient permission for accessing the reports configured in step 1. This is as simple as attaching the following inline policy to the role:
{ "Statement": [ { "Action": [ "s3:GetObject", "s3:GetObjectVersion", "s3:ListBucket" ], "Effect": "Allow", "Resource": [ "arn:aws:s3:::S3BUCKETNAME", "arn:aws:s3:::S3BUCKETNAME/*" ] } ], "Version": "2012-10-17" }
Where S3BUCKETNAME should be replaced with the name of the bucket you specified in step 1.
From the manage dialog for your AWS account in LogicMonitor, on the billing tab, enable billing monitoring. You’ll need to provide the bucket name and path you specified in step 1:
See this topic for how to import your DataSources.
Once these steps are complete, you should see Cost by service, region, account and operation DataSources appear under the account level device, like this:
Products, regions, account ids, and operations will be discovered dynamically as instances via custom Active Discovery methods.
The Cost by tag DataSource is multi-instance, but does not have Active Discovery (AD) enabled by default. As such, you have two options:
The only requirement for monitoring cost associated with tags is that you have the tags enabled as cost allocation tags included your Cost & Usage report.
You can enable AD and auto-discovery of tag values in the DataSource definition, like this: We suggest that you start from the Cost By Tag DataSource, clone it, and edit the AD section. In the AWS Billing Report Attribute field, you should enter your tag key prefixed with ‘user:’ (AWS prepends this in the Cost & Usage report as it’s a user defined tag). All values for the specified key will be discovered, and cost will be monitored for each. So you’ll need a different DataSource for each tag key you want to track costs for.
If you prefer to manually add instances, you can do at the account level device like this:
DataSource – should be the ‘Cost by Tag’ DataSource
Name – should be the Tag value you’d like to monitor cost for
Wildvalue – should be the name of the Tag as it appears in the Cost & Usage report, which will usually be preceded by ‘user:’ to denote a user specified tag
Once complete, data should populate for your new instance within a few minutes.
Once you’ve configured LogicMonitor’s AWS Billing monitoring and data collection has begun, you can visualize this data in a dashboard. Download this JSON template and import it into you account, or create your own custom Dashboard.
In This Article
