LogicMonitor seeks to disrupt AI landscape with $800M strategic investment at $2.4B valuation to revolutionize data centers.

Learn More

    Platform

    Get real-time insights and automation for comprehensive, seamless monitoring with agentless architecture.

  • Infrastructure
    monitoring
  • Cloud monitoring
  • Digital experience
  • AIOPS

      • Solutions

      Whether you work in MSP, Enterprise IT or somewhere in between, the solution is clear.

    By Initiative
    By Industry

      About us

      Get to know LogicMonitor and our team.

    Get to know us
    Services

      Resources

      Explore our blogs, guides, case studies, eBooks, and more actionable insights to enhance your IT monitoring and observability.

    Learn

      Documentation

      Read through our documentation, check out our latest release notes, or submit a ticket to our world-class customer service team.

    Support

    Product Documentation

    Resource Sizing for Performance Optimization and Tuning Recommendations

    Last updated on 22 November, 2023

    The following table provides guidelines on provisioning resources for LogicMonitor components to have optimum performance and reliable monitoring for the Kubernetes cluster:

    Collector SizeMediumLarge 
    Maximum Resources with 1 collector replica1300 resources3600 resources
    Argus and CSC VersionArgus Version – v7.1.2
    CSC Version – v3.1.2    		Argus Version – v7.1.2
    CSC Version – v3.1.2
    Collector VersionGD 33.001 GD 33.002 
    Recommended Argus limits & RequestsCPU Requests – 0.256 core
    CPU Limits – 0.5 core    		CPU Requests – 0.5 core
    CPU Limits – 1 core
    Memory Requests – 250MB
    Memory Limits – 500MB    		Memory Requests – 500MB
    Memory Limits – 1GB

    Recommended Collectorset Controller limits & Requests    		CPU Requests – 0.02 core
    CPU Limits – 0.05 core    		CPU Requests – 0.02 core CPU Limits – 0.05 core
    Memory Requests – 150MB
    Memory Limits – 200MB    		Memory Requests – 150MB
    Memory Limits – 200MB

    Example of Collector Configuration for Resource Sizing

    Let’s say you have about 3100 resources to monitor. You need a large collector single replica with the compatible versions as displayed in the above table to monitor your resources. You can configure the collector size and replica count in the configuration.yaml file as follows: 

    argus:
  collector:
     size: medium
     replicas: 1

    Note: In the size field, you can add the required collector size (Large or Medium) and in the replicas field, you can add the number of required collector replicas.

    Specifying Resource Limits for Collectorset-Controller and Argus Pod

    You can enforce central processing unit (CPU) and memory constraints on your Collectorset-Controller, Argus Pod, and Collector. 
    An example of the collectorset-controller.resources parameter displayed in the following lm-container configuration yaml file:

    collectorset-controller:
   resources:
      limits:
        cpu: "1000m"
        memory: "1Gi"
        ephemeral-storage: "100Mi"
     requests:
       cpu: "1000m"
       memory: "1Gi"
       ephemeral-storage: "100Mi"

    An example of the argus.resources parameter displays in the following lm-container configuration yaml file:

    argus:
   resources:
      limits:
        cpu: "1000m"
        memory: "1Gi"
        ephemeral-storage: "100Mi"
     requests:
       cpu: "1000m"
       memory: "1Gi"
       ephemeral-storage: "100Mi"
    In This Article