LogicMonitor Cloud Monitoring Overview

Last updated on 30 January, 2023

LM Cloud provides a fast, three-step setup wizard that automatically discovers, applies, and scales monitoring for your entire cloud ecosystem. Experience executive-level dashboards and deep-dive technical insights into AWS, GCP, and Microsoft Azure together with other infrastructure on one unified platform.

LM Cloud provides seamless and frictionless setup and API-based monitoring of AWS, GCP, and Microsoft Azure environments, and business-critical SaaS applications, such as Office 365, Salesforce, Zoom, or any supported by Atlassian Statuspage.io.

LM Cloud allows you to monitor your cloud services alongside your existing monitored infrastructure in LogicMonitor. The cloud monitoring strategy includes three components critical to measuring the overall health and performance of cloud infrastructure:

1. Resource Monitoring

  • Performance data, such as metrics for CloudWatch, Azure Monitor, and LogicMonitor Collector (Application, OS-level, and custom).
  • Event data, such as CloudWatch Events and Azure Activity Log Events.

2. Cloud Provider Availability Monitoring

  • Availability data, such as data provided by AWS and Azure status RSS feeds, measured by LogicMonitor Collector, and scheduled maintenance events.
  • Service Limit Utilization data.

3. Return On Investment (ROI) Monitoring

  • Spend data per region, service, or tag.
  • Reserved instances offer expiration dates.

Monitored data for these three components are presented in auto-generated dashboards alongside any monitored data for on-premises infrastructure in LogicMonitor. LM Cloud centralizes monitoring, alerting, and reporting and provides granular data retention up to two years.

How is data collected?

LogicMonitor collects data via the following methods:

  • The application program interface (API) for individual cloud providers, for example, AWS CloudWatch API, AWS EC2 API, Azure Monitor API, and so on.
  • LogicMonitor Collector

Metrics from LM Cloud are presented within LogicMonitor the same way as metrics for all resources and device metrics.

LogicMonitor discovers your cloud resources and adds each resource as a LogicMonitor device. 

DataSources that are pre-configured to perform API calls and queries are automatically applied to these discovered resources. If you also have a Collector deployed within your cloud environment, traditional Collector DataSources based on SNMP, WMI, and so on, will also auto-apply to these discovered resources.

All the existing LogicMonitor reporting, alerting dashboard, and monitoring functionality work the same way once this data is in LogicMonitor.

Do I need a Collector?

A traditional LogicMonitor Collector can provide more comprehensive monitoring for your cloud resources.

A Collector can provide OS-level metrics and application metrics for AWS EC2 instances and Azure VMs, which are not available through their Monitor APIs. For example, a Collector installed within AWS would monitor Apache running on any EC2 instance and traditional OS-level metrics such as Disk Usage and Memory Usage (not reported via AWS CloudWatch).

A Collector is not required for LM Cloud. You will still be able to monitor your AWS and Azure resources via their APIs. However, you will not be able to monitor:

  • Detailed OS-level, application, and custom metrics.
  • Cloud provider availability checks.

How do I view non-resource-specific metrics?

Cloud Provider Availability monitoring includes many metrics that are not tied to a single resource (such as an EC2 instance or a VM), but instead indicate account-level health. These metrics include service limit utilization and cloud provider service disruptions or outages.

LogicMonitor automatically adds an “Account-Level Device” for each new cloud account. All non-resource-specific metrics will be displayed under this device.

Which Cloud Integrations are supported?

LogicMonitor supports the following cloud integrations:

  • Cloud Monitoring
    • Amazon Web Services
    • Google Cloud Platform
    • Azure
  • SaaS Monitoring
    • Zoom
    • Microsoft Office 365
    • Salesforce
    • AirBrake 
  • Lite Monitoring

Note: Access the Cloud Integrations in LogicMonitor by navigating to Resources > Add > Cloud Account .

Which cloud services are monitored?

LM Cloud’s three-component strategy (resource monitoring, cloud provider availability monitor, and ROI monitoring) does not depend on the cloud provider. Currently supported cloud services include Amazon Web Services, Microsoft Azure, and Google Cloud Platform:

Amazon Web Services (AWS)

  • APIGateway
  • ApplicationELB
  • AppStream
  • Athena
  • Aurora
  • Auto Scaling
  • Backups
  • Billing
  • ClassicELB
  • CloudFront
  • CloudSearch
  • CodeBuild
  • Cognito
  • Connect
  • Direct Connect
  • Direct Connect Virtual Interface
  • Database Migration Service
  • Database Migration Service Tasks
  • DocumentDB
  • DynamoDB
  • EBS
  • EC2
  • ECS
  • EFS
  • ElastiCache
  • Elastic Beanstalk
  • Elasticsearch
  • ElasticTranscoder
  • Elalstic Load Balancers
  • EMR
  • EventBridge
  • Kinesis Firehose
  • FSx
  • Glue
  • Kinesis Streams
  • Kinesis Video
  • Lambda
  • MediaConnect
  • MediaConvert
  • MediaPackage Live
  • MediaPackage VOD
  • MediaStore
  • MediaTailor
  • MQ
  • MSK Brokers
  • MSK Clusters
  • NAT Gateway
  • NetworkELB
  • Neptune
  • OpenSearch
  • OpsWorks
  • RDS
  • Redshift
  • Route53
  • Route53Resolver
  • S3
  • SageMaker
  • Service Limits
  • SES
  • SNS
  • SQS
  • Step Functions
  • SWF Activities
  • SWF Workflows
  • Transit Gateways
  • Transit Gateway Attachments
  • VPC TransitGateway
  • VPC NAT Gateway
  • VPN
  • WAF
  • WorkSpaces
  • WorkSpace Directories

Microsoft Azure

  • Advisor
  • Analysis Services
  • API Management
  • Application Gateway
  • Application Insights
  • App Services and App Service Plans
  • Automation Accounts
  • Backup
  • Batch Accounts
  • Cognitive Search and Cognitive Services
  • Cosmos DB
  • Data Factory
  • DataLake Analytics
  • DataLake Store
  • Event Grid Topics
  • Event Hub
  • Express Route Circuit
  • Firewall
  • Front Doors
  • Functions
  • HDInsight Clusters
  • IoT Hub
  • Key Vault
  • Kubernetes Service (AKS)
  • Load Balancers
  • Logic Apps
  • MariaDB Database Server
  • MySQL & PostgreSQL Database Server
  • Network Interfaces
  • Notification Hubs
  • Public IP Address
  • Recovery Services
  • Redis Cache
  • Relay Namespaces
  • Search
  • Service Bus
  • Service Fabric
  • Site Recovery
  • SQL Database
  • SQL Elastic Pools
  • SQL Managed Instances
  • Storage (Blob Storage, File Storage, Queue Storage, Table Storage)
  • Stream Analytics
  • Virtual Machine
  • Virtual Machine Scale Sets
  • Virtual Network Gateways

Google Cloud Platform (GCP)

  • AI Platform
  • App Engine
  • BigQuery
  • Cloud Composer
  • Cloud Dataflow
  • Cloud Dataproc
  • Cloud Filestore
  • Cloud Firestore
  • Cloud Functions
  • Cloud Interconnect
  • Cloud IOT
  • Cloud Memorystore for Redis
  • Cloud Router
  • Cloud Run
  • Cloud SQL
  • Cloud Storage
  • Compute Engine
  • HTTP(S) Load Balancer
  • Pub/Sub
  • Spanner
  • VPN Gateway

How do I get started?

Start by adding your cloud environments into LogicMonitor. You can find instructions for adding your Microsoft Azure environment here, and instructions for adding your Amazon AWS environment here.

If you already have AWS or Azure resources in monitoring and want to adopt LM Cloud, read on here.

In This Article