Limits, Quotas, and Constraints

This document lists some of the most common LogicMonitor resource limits, quotas, and constraints.

Some limits can be adjusted (for example, increased), while other limits cannot be adjusted. In this document, the limits that can be adjusted are referred to as “soft limits”, and the limits that cannot be adjusted are referred to as “hard limits”.

LogicMonitor sets limits based on the historic usage of the resources and you should not need to change preset limits. If you do need to change certain limits, you can contact LogicMonitor Support and submit a ticket for changing the limit. 

Object Quota Recommendations

Most object quota limits are defined at the LogicMonitor object level. For each object, there are two levels of limits assigned to customer portals. When the first limit is reached, LogicMonitor shows an Informative warning. When the second limit is reached, LogicMonitor shows a Critical warning.

The following sections summarize LogicMonitor objects and their respective limits.

Resource Groups

Resource group is a combination of static and dynamic group. The quota for resource groups is calculated based on the ratio of resource groups to devices and according to LogicMonitor best practices. This feature helps you identify problematic configurations, such as a high number of Resource Groups, and warns you before it starts to impact the performance of your portal. This feature does not stop you from performing any actions. 

Customers	Limits (Level)	Type
Enterprise	105 % of committed devices (Informative) 110 % of committed devices (Critical)	Soft Limit
Managed Service Provider (MSP)	95 % of committed devices (Informative) 100 % of committed devices (Critical)	Soft Limit

Website Folders

You can track your website usage against the committed number of websites. If the limit is exceeded, you will see warnings in your Accounts Information page. This feature does not stop you from performing any actions. 

Customers	Limits (Level)	Type
Enterprise	105 % of committed websites (Informative) 110 % of committed websites (Critical)	Soft Limit
Managed Service Provider (MSP)	95 % of committed websites (Informative) 100 % of committed websites (Critical)	Soft Limit

Metrics Collection

The object quota limits for metrics (that is, data) collection is based on the number of regular devices for which customers have purchased licenses from LogicMonitor. Note that cloud devices are not included in the object quota limit for metrics.

On the Accounts Information page, under the Resources table, you can view the Monthly Datapoints Collection Per Device. It indicates the number of metrics collected since the start of the month.

The quota limit for metrics collection is calculated as follows:

• The average per day per device metrics quota limit is set as 2000000 metric collection.
• 30.42 is the average of monthly days in a year. Thus, the average per month per device metrics quota limit is 2000000 * 30.42 = 60840000 metric collection.

Based on the above calculations, the following messages appear on the Accounts Information page:

• Warning message – It is displayed when you reach the average per day per device of 57798000 metric collection. It is indicated in yellow. The warning message is displayed once you ingest 95% of the quota limit metrics. It is 95% of 60840000.
• Critical message – It is displayed when you reach or exceed the monthly quota of 60840000 metric collection. It is indicated in red.

Once you reach or exceed the quota limit, these messages will encourage you to comply with LogicMonitor best practices. These object quota limit messages give you an overall picture of metrics ingested, and warns you before it leads to any issue. Because this is a soft limit, you can continue to perform regular operations. However, you can try to reduce resource usage by reducing the number of DataSources applied on instances, or datapoints defined in the datasources, or the frequency of collecting datapoints. This reduces load on LogicMonitor servers and help in providing uninterrupted service.

You should know the following details about your monitored devices:

• DataSource
• DataSource Instances count
• Datapoint count
• DataSource frequency in seconds

The per month frequency schedule is calculated as:

262828800/DataSource frequency

Here, 262828800 is the total number of seconds in a month.

The metrics collected for a device against a single DataSource is calculated using the following formula:

DataSource Instance count * Datapoint count * per month frequency schedule value = Metrics per month

Example:

Device Name	DataSource	DS Frequency (seconds)	DS Datapoint	DS Instances	DS Monthly Frequency (2628288/DS Frequency)	Monthly Metrics Ingested
DeviceA	Ping	60	10	4	43805	4 * 10 * 43805 = 1752200
DeviceA	dns	180	8	12	14602	12 * 8 * 14602 = 1401792
DeviceA	CPUCores	300	12	4	8761	4 * 12 * 8761 = 420528
DeviceB	Ping	60	10	4	43805	4 * 10 * 43805 = 1752200
DeviceB	dns	180	8	12	14602	12 * 8 * 14602 = 1401792
DeviceC	CPUCores	300	12	4	8761	4 * 12 * 8761 = 420528
DeviceC	Ping	600	10	4	4380	4 * 10 * 4380 = 175200
DeviceC	dns	180	8	12	14602	12 * 8 * 14602 = 1401792
DeviceC	script	300	6	10	8761	10 * 6 * 8761 = 525660

Total Metrics ingested by each device is:

• DeviceA: 1752200 + 1401792 + 420528 = 3574520
• DeviceB: 1752200 + 1401792 = 3153992
• DeviceC: 420528 + 175200 + 1401792 + 525660 = 2523180

Total Monthly Metrics ingested by the customer is:

3574520 + 3153992 + 2523180 = 9251692

To calculate the Average Per Device Monthly Metrics ingested, divide the Total Monthly Metrics ingested by Committed Devices in the license. Thus, if the committed regular devices in the license are 1000, then 9251692/1000 = 9251.692 average per device monthly metrics for the customer. In this case, because the average per month per device metrics quota limit does not exceed, a message is not displayed.