Forum Discussion

Jesse_Hester's avatar
6 years ago

Feature request / gripe: extremely long active-discovery times for AWS billing data sources

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 (?).

1 Reply

Replies have been turned off for this discussion
  • Sarah_Terry's avatar
    Icon for Product Manager rankProduct Manager

    Hi @Jesse Hester,

    Thanks for posting. The billing discovery certainly shouldn't be taking 4 hours! We can do some testing to see if we can reproduce, and optimize. If you set it up for another account & it takes long, I'd suggest reaching out to support so we can try and determine what is going wrong.

    If you haven't already, I'd suggest using the Cost By Tag DataSource as well (which is in our repository by default, but does require a small amount of configuration - see this page).

    We'll also make sure to update the API example for adding an AWS group.