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!
Monitoring AWS EC2 instances, Azure VMs, and GCP Compute Engine instances can be done with LogicMonitor’s Cloud Collector that pulls metrics from CloudWatch, Azure Monitor, and Stackdriver API respectively. However, to collect the operating system and application metrics, a local collector is also required.
Once you have installed the LogicMonitor Collector, you can access the LogicMonitor’s LogicModule library for your cloud resources, including DataSources, EventSources, PropertySources, etc. The specific data for CloudWatch, Azure Monitor, and Stackdriver will continue to be collected via LogicMonitor Collector.
You can view the data collected by the LogicMonitor Collector alongside the CloudWatch, Azure Monitor, and GCP Stackdriver data.
To enable monitoring via a local collector, complete the following steps:
1. Navigate to Resources and click Manage for your AWS / Azure / GCP account.
Note: You can follow these steps while adding a cloud account.
2. On the top-right corner, click Manage.
3. On the Cloud Integrations page, click the Services tab.
4. Select the required services from the list and click the Settings Gear icon.
5. On the Settings page, click the Collector Assignments tab.6. Toggle the Enable Monitoring via local Collector option to enable the monitoring.
7. In the Collector Assignments section, on the top-right corner, click the + icon, to add the collector.
The collector assignments will map Collectors to the EC2 instances, VMs, or Compute Engine instances they should monitor. You can assign Collectors based on EC2, VM, or Compute Engine properties like AWS region or VPC, Azure subnet, or a custom tag. You may also want to add a condition to exclude stopped instances from getting a collector assignment to avoid receiving alerts for DataSources like Ping – you can add ‘&& system.aws.stateName != “stopped”’ to an existing query.
Note: Currently, you can only use properties starting with system.aws, system.azure, and system.gcp.
8. (Optional) You can click the Discovery Settings tab and toggle the Use custom NetScan Frequency option to enable more frequent discovery for the EC2 / VM / Compute Engine service. Enabling this option will allow you to configure LogicMonitor to check for new EC2 / VM / Compute Engine instances up to every 10 minutes (more frequent than the default frequency for all services, which has a minimum of 1 hour). This frequency will only apply to the EC2 / VM / Compute Engine service.
9. Save your changes.After saving, the system.sysinfo property will be automatically populated for the EC2 instances / VMs / Compute Engine instances to which you assigned a Collector, and LogicMonitor DataSources will apply accordingly. The assigned Collectors will run Active Discovery for these DataSources, and you should see instances and data shortly thereafter:
If you disable monitoring via local Collector after it has already been enabled, any data collected by the local Collector will be deleted. CloudWatch/Azure Monitor/Stackdriver metric collection will continue being collected by a LogicMonitor maintained Collector.
LogicMonitor will use the first private IP address listed. You can override this assignment by setting a resource property cloud.primaryIP with the IP address you want LogicMonitor to collect data from.
The last assignment will take priority.
If you configure the EC2 instances that no longer match to be deleted, they will be deleted according to schedule.
If you do not configure the EC2 instances to be deleted, but the instances no longer match the criteria in the EC2 service settings, CloudWatch data collection will stop and local Collector-based data collection will continue (assuming a local Collector was assigned and that the ‘enable monitoring via local Collector’ option is still enabled).
No. When local collector monitoring is enabled for a device, the device is no longer counted as a cloud device and will not be billed as one. (You will not be billed twice for the device, because it will only count as a regular device.)
In This Article