MQ

LogicMonitor currently has two DataSources for monitoring MQ: AWS_MQ_Broker Source: CloudWatch Datapoints: Default Polling Interval: 5 minutes. Additional Configuration Necessary?: No. This DataSource will automatically apply to and start collecting data for any MQ Broker resources discovered for your AWS Account. AWS_MQ_StandbyBroker Source: CloudWatch Datapoints: Default Polling Interval: 5 minutes. Additional Configuration Necessary?: No. This DataSource will automatically apply … Continued

Customizing Azure Monitor DataSources

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.  Prerequisites Customizing the LogicMonitor Datapoint Definition To add dimensions to … Continued

Active Discovery for AWS CloudWatch Metrics

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

Monitoring Amazon Connect

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

GCP Billing Monitoring

LogicMonitor supports monitoring of billing data via Google Cloud Platform (GCP) Billing Export. What data is monitored? Import the following DataSources to monitor GCP Billing. GCP_Billing_CostByOperation_BigQuery – spend monitored per GCP billable operation GCP_Billing_CostByProject_BigQuery – spend monitored per GCP project (relevant for linked billing accounts) GCP_Billing_CostByService_BigQuery – spend monitored per GCP service (e.g. App Engine, … Continued

Adding your GCP environment into LogicMonitor

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

Azure Billing Monitoring Setup

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 Elastic Beanstalk

LogicMonitor has one datasource for monitoring Elastic Beanstalk : AWS_ElasticBeanstalk_Environment – collects basic environment health data from CloudWatch AWS_ElasticBeanstalk_Environment Source: CloudWatch Datapoints: EnvironmentHealth Default Polling Interval: 1 minute. Additional Configuration Required?: No – this datasource will automatically apply to and start collecting data for any Elastic Beanstalk Environments discovered for your AWS Account. NOTE that you can publish custom … Continued

AWS NAT Gateway

LogicMonitor currently has one DataSource for monitoring AWS VPC NAT Gateway performance metrics: AWS_VPC_NATGateway Source: CloudWatch Datapoints: Active connection count Bytes in from destination Bytes in from source Bytes out to destination Bytes out to source Connection attempt count Connection established count Error port allocation Idle timeout count Packets drop count Packets in from destination Packets … Continued