Jesse Hester

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jesse Hester

  • Rank
  1. Earlier this evening I used the REST API to create an AWS group containing an account device for the purposes of billing monitoring. I didn't specify any services to monitor; I only provided a billing bucket and report path prefix. (Side note: the example under (2) at is out of date.) Nearly four hours later, LogicMonitor has discovered a handful of instances for each of the Cost By Service, Cost By Operation, and Cost By Region data sources. It has yet to discover an instance for the Cost By Account data source. (Those four comprise what comes with billing monitoring.) The billing bucket had report files waiting to be retrieved as soon as the account device was created. I have the active discovery schedule for each of the aforementioned data sources set to 15 minutes, though that shouldn't matter because, as stated previously, I force active discovery upon device creation. I have the polling frequency for one of the four data sources set to 1 minute for testing purposes, with the rest set to 1 hour, but that shouldn't matter either, because surely instances are polled at least once when they are discovered, regardless of the frequency setting (?).
  2. Hi Sarah, Thanks for getting back to me. Ideally, upon billing monitoring being enabled, LM would grab all of the billing data present in the billing bucket. The use case here is a client who has had AWS Cost and Usage reports set up for some time before integrating with LM. For my case in particular, going back three months would be satisfactory.
  3. I would like to see the cloud collector for AWS utilize all of the relevant data in the cost and usage reports provided by Amazon. For example, I just enabled billing monitoring for an AWS account, and the billing bucket contains reports for every day in June, but the collector just calculated the month-to-date total costs as of today, though it could have calculated the month-to-date total costs for each day in June and populated the graphs accordingly. It also ignored the reports for May.