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!
Once you’ve added your AWS account to LogicMonitor, your AWS resources will be discovered and displayed in your LogicMonitor account. AWS resources will be displayed with a cloud icon in your device tree, and AWS groups will be displayed with the AWS cube icon. The total number of AWS resources in your account is displayed at the top of the device tree (this count does not include AWS resources added as regular LogicMonitor devices):
A LogicMonitor hosted collector will search for and auto-discover AWS resources every five minutes using our NetScan functionality. Resources will be discovered for each of the AWS Services you selected. After your AWS resources are discovered, a NetScan will run according the the schedule specified in the ‘Auto-Discovery Frequency’ field in your AWS account configuration. You can force a NetScan to run and detect any new AWS resources in your account by selecting ‘Manage’ for your AWS Account group in LogicMonitor and then selecting ‘save’.
Resources will only be discovered based on your selected service types, selected regions and any tag filters you have specified. There are a couple of ways to delete AWS devices:
It’s possible to rename AWS EC2 resources. See Renaming discovered EC2 instances.
For other AWS groups and devices, you cannot change their names in LogicMonitor. AWS devices and groups are named in the following format:
The way that LogicMonitor queries your AWS account for data relies on these naming conventions.
LogicMonitor’s datasource developers set some default thresholds in the AWS datasource definitions. However, since thresholds set in a datasource definition apply globally to all customers, we can’t always set default thresholds that will work for everyone. We recommend that you set thresholds specific to your environment to ensure that your alerting implementation is sufficient and noise-free.
AWS has a maximum of 500 requests per second. If you customize an AWS datasource to have a smaller polling interval OR you have a large number of AWS devices we are collecting data for, this limit could be reached. If LogicMonitor receives a throttling message from AWS for your account, we will automatically begin making data requests less frequently but for more data (so you keep the data granularity).
In This Article