LogicMonitor DataSources that use the ‘Azure Monitor’ collection method can be customized to collect additional metrics, different aggregation methods, or metrics with specific dimensions. The JSON path field in each datapoint controls which parameters get passed by LogicMonitor’s Cloud Collector into the Azure Monitor API request. For more information about Azure Monitor, see Azure Monitor documentation from Microsoft. … Continued
You can automatically track your Amazon Web Services (AWS) CloudWatch custom metrics in LogicMonitor Cloud by enabling Active Discovery in a DataSource. Active Discovery regularly checks for changes in your monitored environment and updates the relevant resource properties. For more information, see “What is Active Discovery?“ Getting Metrics from AWS CloudWatch To retrieve the AWS CloudWatch … Continued
To monitor Amazon Connect service integrations, you need to add the AWS Connect DataSource to your LM portal account and add AWS Connect instances. Add the AWS Connect DataSource The AWS Connect DS gathers metrics reported by AWS CloudWatch for each monitored AWS Connect instance. To add the AWS Connect DataSource to your LM account: … Continued
LogicMonitor supports monitoring of billing data via Google Cloud Platform (GCP) Billing Export. Import the following DataSources to monitor GCP Billing. For more information on creating DataSources, see Creating a DataSource. Enable GCP Billing Monitoring in LogicMonitor To enable the GCP Billing Monitoring in LogicMonitor, complete the following steps: 1. Set up your GCP account on … Continued
To add your GCP account into LogicMonitor, complete the following steps: Requirements Note: You may want to create a service account in the Google Cloud Platform portal before you start so that you have the Project ID and Secret Key available for setting up permissions. For more information, see Setting up a GCP account. Note: … Continued
LogicMonitor leverages the Cost Management API to monitor Microsoft Azure billing data. You can set up the monitoring for Azure billing by entering your Microsoft Azure Subscription ID in LogicMonitor. For more information, see What is Microsoft Cost Management and Billing? Setting up Monitoring for Azure Billing Azure Billing Modules Module Type Billing Method Description … Continued
AWS Reserved instance offers can be a great way to save money, but it can be challenging to keep track of all of the expiration dates when you’re managing multiple offers. While an expired offer likely won’t impact performance of your cloud infrastructure, it can have significant effect on your bill. With LogicMonitor’s EC2 Reserved … Continued
In addition to monitoring cloud resource health and performance, we recommend that you monitor your cloud provider as a service you rely on. This means monitoring account level metrics that could impact the availability and/or performance of your resources, such as availability & service limit utilization. Hitting the service and region specific limits imposed by … Continued
LogicMonitor automatically discovers AWS and Azure resources for desired services and regions when you add your AWS and Azure environments for monitoring. By default, resources are added with the following naming scheme: AWS: Region:resourceName:resourceID (e.g. US-E1:ProdApp1:ib36178943) Azure: Region:serviceName:resourceName (e.g. US-E1:vm:ProdApp1) You may want to change how resources are named when LogicMonitor discovers them. Such a … Continued
Adding a Local Collector to your AWS, Azure, or GCP platform provides the most detailed access to important data about your AWS EC2 instances, Azure VMs, and GCP compute engine instances. Installing a Local Collector allows you to collect full OS and application-level metrics within your cloud infrastructure. LogicMonitor collects health metrics for cloud servers … Continued