Adopting Cloud Monitoring for Existing Resources

If you’re an existing customer, you may already be monitoring AWS or Microsoft Azure resources with LogicMonitor. The steps to take advantage of LogicMonitor Cloud Monitoring features largely depend on how you are monitoring AWS, Azure, or GCP resources now. Identify the scenario that matches your own, and follow the steps corresponding to that scenario: Currently Monitoring … Continued

Adding Microsoft Azure Cloud Monitoring

Monitor the state of your Azure deployment, underlying services, and license usage. Monitoring your Azure environment with LogicMonitor helps you to manage performance and identify potential faults. Requirements Your LogicMonitor account registered as an App in Microsoft Azure and the following credentials: For more information, see How to register apps in Microsoft Azure documentation. Adding … Continued

Adding Amazon Web Services Environment into LogicMonitor

With LogicMonitor, monitor Amazon Web Services (AWS) accounts and the underlying services and license usage. This allows you to identify faults and manage performance. Adding AWS into LogicMonitor involves creating an AWS Policy, Role, and exchanging a series of identifiers with LogicMonitor. To add an AWS account to LogicMonitor from the LogicMonitor console, initiate the LogicMonitor and AWS credential exchange and integration (Account ID, … Continued

LM Cloud Monitoring Overview

LM Cloud provides seamless setup and API-based monitoring of AWS, GCP, and Microsoft Azure environments. It also supports business-critical SaaS applications, such as Office 365, Salesforce, Zoom, or any supported by Atlassian Statuspage.io. It includes a fast, three-step setup wizard that automatically discovers, applies, and scales monitoring for your entire Cloud ecosystem. LM Cloud offers … Continued

Cloud Data Collection

Similar to how the Poll Now feature can be used to troubleshoot traditional, local Collector-based LogicModules, you can use Poll Now to troubleshoot CloudWatch data collection.  Remember that CloudWatch data is collected via a LogicMonitor maintained Collector.  Poll Now provides the visibility you need to identify potential issues in data collection, such as permission issues or DataSource … Continued

SES

LogicMonitor currently has the following DataSources for monitoring Simple Email Service performance metrics: AWS_SES – reports per-instance SES statistics   AWS_SES Source: CloudWatch Datapoints: Bounces Complaints Deliveries Rejects Sends SuccessRate Default Polling Interval: 5 minutes. Additional Configuration Required?: Yes, see below. Configuration By default, only account-wide metrics for SES are available via CloudWatch. To get metrics … Continued

AWS VPN

LogicMonitor currently has one DataSource for monitoring AWS VPN performance metrics:  AWS_VPN Source: CloudWatch Datapoints: TunnelState TunnelDataIn TunnelDataOut Default Polling Interval: 5 minutes.  Additional Configuration Required?: No. This datasource will automatically apply to the VPN  instances discovered for your AWS account and start collecting data.

CloudWatch Costs Associated with Monitoring

LogicMonitor’s AWS DataSources leverage the CloudWatch API to collect data for your AWS resources. Depending on which AWS services and how many resources you monitor, you may see CloudWatch costs associated with LogicMonitor’s AWS Cloud Monitoring. LogicMonitor makes one API call per DataSource per Resource. Since the AWS charge is based on the number of datapoints … Continued