Support Center

To better serve you during these uncertain times, we will be hosting a weekly support webinar. We’ll cover topics like LogicMonitor admin basics as well as ways to monitor a remote work environment. Tune in every Wednesday at 11:00am PST.

Sign up here
Submit a Ticket Icon Right Release Notes Icon Right LM Academy Icon Right

To better serve you during these uncertain times, we will be hosting a weekly support webinar. We’ll cover topics like LogicMonitor admin basics as well as ways to monitor a remote work environment. Tune in every Wednesday at 11:00am PST.

Sign up here
Support > Lm Cloud > Getting Started Lm Cloud > 1 Lm Cloud

1. About LM Cloud

LM Cloud allows you to comprehensively monitor your cloud services in LogicMonitor alongside your existing monitored infrastructure, giving you an end-to-end view of your entire hybrid infrastructure performance. This comprehensive visibility is achieved with a cloud monitoring strategy that includes monitoring for the three components critical to measuring overall health of cloud infrastructure:

  • Resource Monitoring

    • Performance data

      • CloudWatch metrics
      • Azure Monitor metrics
      • LogicMonitor Collector metrics (application, os-level, and custom)
    • Event data

      • CloudWatch Events
      • Azure Activity Log Events
  • Cloud Provider Availability Monitoring

    • Availability data

      • AWS & Azure Status RSS feed events
      • Availability as measured by LogicMonitor Collector
      • Scheduled maintenance events
    • Service Limit Utilization data
  • ROI Monitoring

    • Spend data

      • per region
      • per service
      • per tag
    • Reserved instance offer expiration data

Monitored data for these three components is presented in auto-generated dashboards alongside any monitored data for on-premises infrastructure you have in LogicMonitor.  Along with the advantages of centralized monitoring, alerting, reporting and dashboards, you will also benefit from LogicMonitors granular data retention (up to two years of data storage at full granularity).


How is data collected?

LogicMonitor collects data via the following methods:

  • Cloud Provider API (think AWS CloudWatch API, AWS EC2 API, Azure Monitor API)
  • LogicMonitor Collector

In LogicMonitor, metrics from both sources are represented with the same datasource infrastructure that all other LogicMonitor device metrics are. LogicMonitor discovers your cloud resources and adds each resource as a LogicMonitor device. Datasources that are pre-configured to perform API calls and queries will be automatically applied to these discovered resources. If you additionally have a Collector deployed within your cloud environment, traditional Collector DataSources based on SNMP, WMI, etc. will auto-apply to discovered resources as well.  All existing LogicMonitor reporting, alerting, dashboard and monitoring functionality works the same way once this data is in LogicMonitor.

Do I need a Collector?

Per the above section, a traditional LogicMonitor Collector can provide more comprehensive monitoring for your cloud resources.  Specifically, a Collector can provide more metrics for AWS EC2 instances and Azure VMs than those provided via AWS and Azure APIs (CloudWatch and Azure Monitor APIs, respectively), such as OS level metrics and application metrics.  For example, a Collector installed within AWS would be able to monitor Apache running on any EC2 instances out of the box, in addition to traditional OS level metrics such as Disk Usage and Memory Usage (not reported via CloudWatch).

That being said, the use of a Collector is not required.  Without a Collector, you’ll still get monitoring for your AWS / Azure resources via AWS / Azure APIs, but you will miss out on:

  • Collector detailed OS, application and, potentially, custom metrics
  • Cloud provider availability checks made via Collector

How are non-resource specific metrics displayed?

Cloud Provider Availability monitoring includes many metrics that are not tied to a single resource (e.g., an EC2 instance or a VM), but rather are indicative of account-level health. These metrics include service limit utilization, and cloud provider service disruptions or outages. In order to easily and accurately display these metrics in LogicMonitor, we will automatically add an “Account-Level Device” for each new cloud account. All non-resource specific metrics will be displayed under this device. See the image below for an example:

 

What cloud services are monitored?

Initially, LM Cloud provides support for both AWS and Azure.  But LM Cloud’s three component strategy (resource monitoring, cloud provider availability monitoring, roi monitoring) is cloud provider agnostic, enabling support for additional cloud providers moving forward. Currently supported services include: 

AWS:

Azure:

Google Cloud Platform:

  • App Engine
  • Cloud Functions
  • Cloud Router
  • Cloud SQL
  • Cloud Storage
  • Compute Engine
  • HTTP(S) Load Balancer
  • VPN Gateway

How do I get started? 

You’ll need to start by adding your Azure and/or AWS environments into LogicMonitor to be monitored. You can find instructions specific to adding your Azure environment here, and instructions specific to adding your AWS environment here.

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

In this Article: