Monitoring Cloud Service Limit Utilization | LogicMonitor

Product Documentation

About LogicMonitor
- Overview
- Technical Support
  - Support Overview
  - Accessing Support Resources
Getting Started
- Implementation Readiness
  - LogicMonitor Implementation Readiness Recommendations for Enterprise Customers
  - Top Dependencies for LogicMonitor Enterprise Implementation
- LogicMonitor Tutorial
- Advanced LogicMonitor Setup
LogicMonitor Concepts
- Limits, Quotas, and Constraints
Collectors
- Collector Overview
- Collector Installation
- Collector Configurations
- Collector Management
- Collector Integrations
- Collector Troubleshooting
Devices
- Adding and Managing Devices
- Device Groups
- Resources Page Overview
- Device DataSources and Instances
- Netscans
Dashboards and Widgets
- Managing Dashboards
- Managing Widgets
- Widget Types
Alerts
- About Alerts
- Alert Discovery
- Responding to Alerts
AIOps
- Anomaly Detection
  - Anomaly Detection Visualization
- Forecasting
  - Data Forecasting
- Topology Mapping
- AIOps for Alerting
LM Service Insight
- About LM™ Service Insight
- Adding Services
- Managing Services
LogicModules
- LogicModule Overview
- LM Exchange
  - LM Exchange
- DataSources
- Data Collection Methods
- Datapoints
- Active Discovery
- Groovy Support
- Powershell Support
  - Creating PowerShell Script Datasources
  - Using PowerShell Scripts in LogicMonitor
- ConfigSources
- EventSources
- Property Sources
  - Creating PropertySources
- TopologySources
  - TopologySource Overview
  - TopologySources Scripts
- AppliesTo
  - AppliesTo Scripting Overview
  - User-Defined AppliesTo Functions
- JobMonitors
- SNMP sysOID Maps
Reports
- Which report should I use?
- Creating & Managing Reports
- Scheduling a Report for Auto-Delivery
- Creating a Report Group
- Report Types
Security
- Two-Factor Authentication
- Single Sign On
- Multi Sign-On
- Configuring the Azure Active Directory SSO Integration
- LogicMonitor Security Best Practices
- Log4j Security Vulnerabilities
Settings
- About the Account Information Page
- About Audit Logs
- Message Templates
  - Alert Messages
  - New User Message
- Users and roles
Terminology and Syntax
- Scripting Support
LM Logs
- LM Logs Overview
- Log Ingestion
- Logs Query Language
- Reviewing Logs and Log Anomalies
- Log Processing Pipelines
- Log Alert Conditions
- LM Logs Roles and Permissions
- LM Logs Usage Monitoring
- Troubleshooting Logs
LM APM
- LM APM Overview
- Push Metrics
- OpenMetrics Integration
  - OpenMetrics DataSource Wizard
  - OpenMetrics Monitoring
- Distributed Tracing
- Synthetics
Cloud Monitoring
- Getting Started
- Amazon Web Services
- Microsoft Azure
- Google Cloud Platform (GCP)
SaaS Monitoring
- Airbrake Monitoring
- Microsoft Office 365 Monitoring
- SaaS Lite Monitoring
- Salesforce Monitoring
- Zoom Monitoring
Container Monitoring
- Kubernetes
- Docker
  - Docker Monitoring
Website Monitoring
- About Websites
- Adding and Managing Websites
- Website Groups
  - Adding Website Groups
  - Editing and Deleting Website Groups
Monitoring Solutions
- Applications and Databases
- Backup and Recovery Systems
- Networking and Firewalls
- Operating Systems and Virtualization
- Server and operations Hardware
- Storage Systems
- Network Traffic Flow
Workflow Integrations
- ServiceNow
  - LogicMonitor ServiceNow CMDB Integration
    - Getting Started with the LogicMonitor ServiceNow CMDB Integration
    - ServiceNow CMDB Update Set: Auto-Balanced Collector Groups
  - Service Graph Connector for LogicMonitor
    - Getting Started with the Service Graph Connector for LogicMonitor Application
- Ansible Integration
- StackStorm
- Terraform Integration
- Microsoft Teams
  - Microsoft Teams Integration Overview
  - Microsoft Teams Integration Setup
Alert Integrations
- Alert Integrations Overview
- Autotask Integration
- Campfire Integration
- ConnectWise Integration
- Custom Email Delivery
- Custom HTTP Delivery
- Integrations Logs
- PagerDuty Integration
- Puppet 4 Integration
- Puppet Integration
- ServiceNow (Incident Management) Integration
- Slack Integration
- Zendesk Integration
Mobile
- About LogicMonitor’s Mobile View and Application
- Responding to Alerts from a Mobile Device
- Viewing Alerts from a Mobile Device
- Viewing Dashboards from a Mobile Device
- Viewing Graphs from a Mobile Device
REST API Developers Guide
- Rest API Overview
- REST API v3
  - REST API v3 Swagger Documentation
  - LogicMonitor v3 SDK
- REST API v2
  - About REST API v2
  - Creating Services via the API
- Rest API v1
RPC API - Deprecated
- About LogicMonitor’s RPC API (Deprecated)
Training and Certification
- LogicMonitor Certified Professional Exam Information
- LogicMonitor Training and Certification

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 AWS and Azure can impact your ability to scale your applications. For example, hitting your EC2 service limit can prevent an Auto Scaling group from scaling to support the load of your application. With LogicMonitor’s suite of AWS and Azure Service Limit DataSources you’ll not only get out of the box monitoring for your service limits, but you’ll also benefit from LogicMonitor’s built in thresholds and receive alerts when you’re above a reasonable utilization percentage. The data collection for these DataSources occurs via a LogicMonitor maintained Cloud Collector.

LogicMonitor currently has the following DataSources for monitoring service limits:

AWS_EC2_ServiceLimits (limits per region)
AWS_SES_ServiceLimits
AWS_AutoScaling_ServiceLimits
Azure_VM_ServiceLimits
Azure_Storage_ServiceLimits
Azure_Network_ServiceLimits
AWS_ClassicELB_ServiceLimits
AWS_EC2_TrustedAdvisorServiceLimits (limits per instance type)

Each of these DataSources discovers regions as instances (per subscription for Azure) and monitors limits, usage, and percent usage.