Product Documentation

Adopting Cloud Monitoring for existing Resources

If you’re an existing customer, you may already be monitoring AWS and/or Azure resources with LogicMonitor.  The steps to take advantage of LM Cloud largely depend on how you are monitoring AWS and/or Azure resources now.  Identify the scenario that matches your own and follow the steps in the article below corresponding to that scenario number:

  1. Currently getting Collector metrics & CloudWatch metrics: I am monitoring AWS EC2 instances and/or Azure VMs as traditional LogicMonitor devices, and I’ve already added my AWS and/or Azure account into LogicMonitor.
  2. Currently getting Collector metrics, but no CloudWatch metrics: I am monitoring AWS EC2 instances and/or Azure VMs  as traditional LogicMonitor devices, but I have not added my AWS and/or Azure account into LogicMonitor.
  3. Currently only getting CloudWatch metrics: I’ve added my AWS and/or Azure account into LogicMonitor, but I’ve not added EC2 instances and/or VMs as traditional LogicMonitor devices to get local Collector metrics.

Case 1:

If you already have an AWS or Azure account monitored in LogicMonitor, you can do the following to take advantage of the new features with LM Cloud:

  1. Enable monitoring via local Collector in your existing AWS / Azure account – gets you Collector metrics in the same view in which you already see CloudWatch / Azure Monitor API metrics. This will result in duplicate monitoring of the Collector data (once for the traditional version of the device and now once for the cloud version of the device). During your free trial period of LM Cloud, this duplicate monitoring will not cost you, and at the end of it, you can choose to:
    • Delete the traditional version of device (would lose history older than 6 months) – provides you with a unified view. Note that there may be dashboard / report / alerting configuration implications for this choice, if they all set up around these devices.
    • Turn off local Collector monitoring for AWS EC2 instances / Azure VMs, and keep traditional version of device – means you maintain separate views (as was already the case).
  2. Import new LogicModules – gets you additional monitoring for resources, cloud provider availability, and billing.
  3. Set up LogicMonitor’s custom event integrations – enables you to achieve a visual event stream in LogicMonitor that you can use to correlate events with performance data.

Case 2:

If you haven’t already added an AWS or Azure account into LogicMonitor, you will need to do so to take advantage of LM Cloud:

  1. Add AWS / Azure account into LogicMonitor – Enables you to get account level metrics (think: service limits, cloud provider availability), and monitor Collector data +  optionally also  CloudWatch / Azure Monitor data in the same view, while taking advantage of LogicMonitor’s automated discovery.  It’s possible CloudWatch / Azure Monitor data is not desired, in which case the EC2 & Azure Virtual Machines DataSources can be disabled.  Enabling monitoring via local Collector will result in duplicate monitoring of the Collector data (once for the traditional version of the device and now once for the cloud version of the device). During your free trial period of LM Cloud, this duplicate monitoring will not cost you, and at the end of it, you can choose to:
    • Delete traditional version of device (would lose history older than 6 months) – provides you with a unified view. Note that there may be dashboard / report / alerting configuration  implications in this case, if they are all set up around these devices.
    • Turn off local Collector monitoring for AWS EC2 instances / Azure VMs, and keep traditional versions of devices – means you maintain separate views OR that you entirely remove the EC2 / VM service from monitoring for AWS / Azure account (but keep monitoring other services & account level data).
  2. Import new LogicModules – gets you additional monitoring for resources, cloud provider availability, and billing.
  3. Set up LogicMonitor’s custom event integrations – enables you to achieve a visual event stream in LogicMonitor that you can use to correlate events with performance data.

Case 3:

If you already have an AWS or Azure account monitored in LogicMonitor, you can do the following to take advantage of the new features with LM Cloud:

  1. Enable monitoring via local Collector in your existing AWS / Azure account – gets you Collector metrics in the same view in which you already see CloudWatch / Azure Monitor API metrics.
  2. Import new LogicModules – gets you additional monitoring for resources, cloud provider availability, and billing.
  3. Set up LogicMonitor’s custom event integrations– enables you to achieve a visual event stream in LogicMonitor that you can use to correlate events with performance data.