Best Practices for Practitioners: Module Configuration
Overview LogicModules, or Modules, are fundamental building blocks used in LM Envision that enable comprehensive monitoring, data collection, and system configuration management across your devices in your IT stack. This guide consolidates best practices for configuring the different types of Modules, including DataSources, PropertySources, ConfigSources, EventSources, LogSources, TopologySources, and JobMonitors. Following these guidelines ensures optimal performance, maintainability, and effectiveness of your monitoring setup. Key Principles Maintain consistent device naming conventions across all Modules to ensure clarity and ease of management Implement precise AppliesTo scripting logic to target the correct resources and avoid unnecessary monitoring Provide comprehensive documentation in descriptions and technical notes to support future maintenance Configure appropriate collection intervals based on the criticality and nature of monitored data Implement proper access control through Resource Group level access control to maintain security and compliance Test thoroughly before deployment using built-in IDE testing capabilities Configuration Best Practices Naming and Organization Use descriptive, standardized naming patterns (e.g., Vendor_Product_Monitor for DataSources) Avoid spaces in unique identifier names to prevent potential system issues Create meaningful resource labels that clearly indicate the module's purpose Group related modules logically while maintaining the visibility of primary instrumentation Use proper capitalization and consistent formatting in all naming elements Documentation and Metadata Include clear, concise descriptions that explain what the module monitors Document all technical requirements and dependencies in technical notes Specify required credentials, permissions, or system configurations Maintain version notes when committing changes Include relevant links to vendor documentation or additional resources Configuration Management Set appropriate collection intervals based on data criticality and system impact Configure meaningful alert thresholds and transition intervals Implement precise AppliesTo scripting to target specific resources Use property substitution instead of hardcoded values where possible Maintain clear alert messages with actionable information or customize alert messaging with pertinent information Data Collection Validate data types and ranges to prevent spurious alerts Implement appropriate error handling and timeout settings Use standardized data collection methods based on the target system Configure proper encoding and parsing options for log collection Implement efficient filtering to reduce unnecessary data collection Access Control Assign appropriate Access Groups to control module visibility and management Maintain at least one Access Group per module Review and update access permissions regularly Consider role-based access requirements when configuring new modules Document access control decisions and requirements Testing and Validation Use built-in testing capabilities before deployment Verify resource targeting through AppliesTo testing Validate data collection scripts and filters Verify access control settings work as intended Use script testing tools to validate complex logic before deployment Test alert thresholds and notification configurations Verify access control settings work as intended Best Practices Checklist Initial Setup ✅ Choose the appropriate module type based on monitoring requirements ✅ Follow standardized naming conventions ✅ Configure meaningful resource labels ✅ Set appropriate Module group membership (or leave ungrouped if no grouping exists) ✅ Document purpose and requirements Configuration ✅ Set appropriate collection intervals ✅ Test and configure accurate AppliesTo criteria ✅ Set up proper access controls ✅ Configure data collection parameters ✅ Set up appropriate filters and thresholds Documentation ✅ Complete all required description fields ✅ Add detailed technical notes ✅ Document dependencies and requirements ✅ Include relevant examples and use cases ✅ Add version notes for changes Testing ✅ Test AppliesTo scripting to verify correct resource targeting ✅ Validate data collection ✅ Verify alert configurations ✅ Test access controls ✅ Validate filters and thresholds Maintenance ✅ Review and update regularly ✅ Monitor for performance impacts ✅ Update documentation as needed ✅ Verify access controls remain appropriate ✅ Maintain version history Conclusion Effective Module configuration is crucial for maintaining a robust monitoring environment. By following these best practices, organizations can ensure their LM Envision implementation remains scalable, maintainable, and effective. Regular review and updates of these configurations, combined with proper documentation and testing, will help maintain the health and efficiency of your monitoring system. Remember to adapt these practices to your specific needs while maintaining the core principles of clarity, efficiency, and security. Additional Resources DataSources Configuration PropertySource Configuration AppliesTo Function Configuration SNMP SysOID Map Configuration JobMonitor Configuration Examples of JobMonitor Monitoring ConfigSource Configuration TopologySource Configuration EventSource Configuration LogSource Overview Modules Management Access Groups for ModulesBest Practices for Practitioners: Modules Installation and Collection
Overview LogicMonitor LogicModules are powerful templates that define how resources in your IT stack are monitored. By providing a centralized library of monitoring capabilities, these modules enable organizations to efficiently collect, alert on, and configure data from various resources regardless of location, continuously expanding monitoring capabilities through regular updates and community contributions. Key Principles Modules offer extensive customization options, allowing organizations to tailor monitoring to their specific infrastructure and requirements. The Module Toolbox provides a single, organized interface for managing and tracking module installations, updates, and configurations. Available or Optional Community-contributed modules undergo rigorous security reviews to ensure they do not compromise system integrity. Regular module updates and the ability to modify or create custom modules support evolving monitoring needs. Installation of Modules Pre-Installation Planning Environment Assessment: Review your monitoring requirements and infrastructure needs Identify dependencies between modules and packages Verify system requirements and compatibility Permission Verification: Ensure users have the required permissions: "View" and "Manage" rights for Exchange "View" and "Manage" rights for My Module Toolbox Validate Access Group assignments if applicable Installation Process Single Module Installation: Navigate to Modules > Exchange Use search and filtering to locate desired modules Review module details and documentation Select "Install" directly from the Modules table or details panel Verify successful installation in My Module Toolbox Package Installation: Evaluate all modules within the package Choose between full package or selective module installation For selective installation: Open package details panel Select specific modules needed Install modules individually Conflict Resolution: Address naming conflicts when detected Carefully consider before forcing installation over existing modules Document any forced installations for future reference Post-Installation Steps Validation: Verify modules appear in My Module Toolbox Check module status indicators Test module functionality in your environment Documentation: Record installed modules and versions Document any custom configurations Note any skipped updates or modifications Core Best Practices and Recommended Strategies Module Management Regular Updates: Consistently check for and apply module updates to ensure you have the latest monitoring capabilities and security patches. Verify changes prior to updating modules to ensure no potential loss of historic data when making changes to AppliesTo, datapoints, or active discovery Review skipped updates periodically to ensure you're not missing critical improvements. Selective Installation: Install only the modules relevant to your infrastructure to minimize complexity. When installing packages, choose specific modules that align with your monitoring requirements. Version Control: Maintain a clear record of module versions and changes. Use version notes and commit messages to document modifications. Customization and Development Custom Module Creation: Develop custom modules for unique monitoring needs, focusing initially on PropertySource, AppliesTo Function, or SNMP SysOID Maps. Ensure custom modules are well-documented and follow security best practices. Careful Customization: When modifying existing modules, understand that changes will mark the module as "Customized". Keep track of customizations to facilitate future updates and troubleshooting. Security and Access Management Access Control: Utilize Access Groups to manage module visibility and permissions. Assign roles with appropriate permissions for module management. Community Module Evaluation: Thoroughly review community-contributed modules before installation. Rely on modules with "Official" support when possible. Performance and Optimization Filtering and Organization: Utilize module filtering capabilities to efficiently manage large module collections. Create and save custom views for quick access to relevant modules. Module Usage Monitoring: Regularly review module use status to identify and remove unused or redundant modules. Optimize your module toolbox for performance and clarity. Best Practices Checklist ✅ Review module updates monthly ✅ Install only necessary modules ✅ Document all module customizations ✅ Perform security reviews of community modules ✅ Utilize Access Groups for permission management ✅ Create saved views for efficient module management ✅ Periodically clean up unused modules ✅ Maintain a consistent naming convention for custom modules ✅ Keep track of module version histories ✅ Validate module compatibility with your infrastructure Conclusion Effectively managing LogicMonitor Modules requires a strategic approach that balances flexibility, security, and performance. By following these best practices, organizations can create a robust, efficient monitoring environment that adapts to changing infrastructure needs while maintaining system integrity and performance. Additional Resources Modules Overview Modules Installation Custom Module Creation Tokens Available in LogicModule Alert Messages Deprecated LogicModules Community LM Exchange/Module ForumBest Practices for Practitioners: Collector Management and Troubleshooting
Overview The LogicMonitor Collector is a critical Software as a Service (SaaS) component designed to collect performance metrics across diverse IT infrastructures. It provides a centralized, intelligent monitoring solution to gather data from hundreds of devices without requiring individual agent installations. By encrypting and securely transmitting data via SSL, the Collector offers a flexible approach to infrastructure monitoring that adapts to complex and diverse network environments. Key Principles Implement a strategic, unified approach to infrastructure monitoring that provides comprehensive visibility across diverse environments Ensure collectors are lightweight, efficient, and have minimal performance impact on monitored resources Maintain robust security through encrypted data transmission and carefully managed credential handling Design a monitoring infrastructure that can dynamically adjust to changing network and resource landscapes Regularly review, tune, and update collector configurations to maintain optimal monitoring performance Comprehensive Collector Management Collector Placement Strategies Strategic Location Install collectors within the same network segments as monitored resources Choose servers functioning as syslog or DNS servers for optimal placement Avoid monitoring across vast internet connections, firewalls, or NAT gateways Sizing Considerations Select appropriate collector size based on expected monitoring load Consider available memory and system resources Understand collector type limitations (e.g., Windows collectors can monitor both Windows and other devices, while Linux collectors are limited to devices) Network and Security Configuration Configure unrestricted monitoring protocols (SNMP, WMI, JDBC) Implement NTP synchronization for accurate time reporting Use proxy servers if direct internet connectivity is restricted Configure firewall rules to allow necessary collector communications Collector Groups Organize collectors logically: By physical location By customer (for MSPs) By environment (development, production, etc.) Utilize Auto-Balanced Collector Groups (ABCG) for dynamic device load sharing Version Management Schedule regular updates Choose appropriate release types (MGD, GD, EA) Maintain update history for tracking changes Use downgrade option if experiencing version-specific issues Logging and Troubleshooting Log Management Adjust log levels strategically: Trace: Most verbose (use sparingly) Debug: Detailed information for troubleshooting Info: Default logging level Warn/Error: Issue-specific logging Configure log file retention in wrapper.conf Send logs to LogicMonitor support when collaborating on complex issues Troubleshooting Specific Environments Linux Collectors Check Name Service Caching Daemon (NSCD) configuration Verify SELinux settings Use getenforce or sestatus to check SELinux status Temporarily set SELinux to Permissive mode for debugging Windows Collectors Ensure service account has "Log on as a service" rights Check local security policy settings Resolve Error 1069 (logon failure) by updating user rights Advanced Techniques Credential Management Integrate with Credential Vault solutions: CyberArk Vault Delinea Vault Use dual account configurations for credential rotation Collector Debug Facility Utilize the command-line interface for remote debugging Run debug commands to troubleshoot data collection issues Performance and Optimization Regularly monitor collector performance metrics Tune collector configuration based on monitoring load Disable Standalone Script Engine (SSE) if memory is constrained Implement proper log and temporary file management Maintenance Checklist ✅ Regularly update collectors ✅ Monitor performance metrics ✅ Review collector logs ✅ Validate data collection accuracy ✅ Test failover and redundancy configurations ✅ Manage Scheduled Down Time (SDT) during maintenance windows Conclusion Successful LogicMonitor Collector management is a dynamic process that requires strategic planning, continuous optimization, and a deep understanding of your specific infrastructure needs. The key to effective monitoring lies in strategically placing collectors, configuring them appropriately, and regularly reviewing their performance and configuration. By following these best practices, organizations can create a robust, adaptable monitoring strategy that provides comprehensive visibility into their IT ecosystem. Additional Resources Management and Maintenance: Viewing Collector Events Managing Collector Logs Adding SDT to Collector Adding Collector Group Collector Version Management Integrating with Credential Vault Integrating with CyberArk Vault for Single Account Integrating with CyberArk Vault for Dual Account Troubleshooting: Troubleshooting Linux Collectors Troubleshooting Windows Collectors Collector Debug Facility Restarting CollectorBest Practices for Practitioners: Service Insights
Overview Modern IT infrastructure spans cloud and on- & off-premises environments, making traditional instance-based monitoring at times insufficient for understanding proper service health. LM Service Insights addresses this challenge by aggregating performance data across multiple resources and locations to provide meaningful service-level visibility. This approach is particularly valuable in dynamic environments where individual instance health may not reflect overall service status and where historical performance data needs to be preserved despite infrastructure changes. Key Principles Service-level monitoring revolutionizes infrastructure oversight by focusing on collective resource performance rather than individual components. This approach is essential for environments where services span multiple containers, cloud resources, and on and off-premises systems. Key benefits include: Maintained visibility across dynamic infrastructure changes Meaningful aggregation of service-wide performance metrics Preserved historical data independent of instance lifecycle Reduced alert noise while capturing critical issues Better alignment between technical metrics and business service delivery When to Use Service Insights Recommended for: Monitoring ephemeral applications running across multiple containers Tracking performance of cloud-based services Managing complex, distributed infrastructure Maintaining visibility into ephemeral or dynamic environments Not Recommended for: Simple up/down status monitoring Tracking discrete value metrics Environments with consistently defined performance ranges Recommended Implementation Strategies Creating Effective Services Service Composition Group-related resources that contribute to a single service Include instances across multiple devices or cloud resources Ensure comprehensive coverage of your application ecosystem Membership Configuration Choose re-evaluation frequency based on environment dynamics: 5 Minutes: For highly dynamic environments (containerized apps, auto-scaling groups) 30 Minutes: For moderately changing infrastructures 1 Day: For stable, less-frequently changing environments Metric Selection and Aggregation Select metrics that represent unique and true service-level performance Use aggregate data collection methods Include both performance and availability indicators Create complex datapoints for nuanced service health assessment Alert Configuration Alerting Strategies Implement multi-layered alerting: Dynamic thresholds for adaptive, noise-reduced monitoring Static thresholds for critical, well-defined alert conditions Configure alerts at the service level to capture broader performance issues Use service-level alerts to complement existing resource-level monitoring Advanced Techniques Service Groups Create logical groupings of related services Simplify navigation and management of complex infrastructures Enable hierarchical monitoring strategies Optimization Tips and Quick Access Utilize the Favorites tab for frequently monitored services Create custom views that highlight critical services Leverage breadcrumbs and focus features for efficient navigation Pro Tip: Treat Service Insights as a dynamic tool. Continuously learn, adapt, and refine your approach to match your evolving infrastructure needs. Best Practices Checklist ✅ Start with a representative subset of infrastructure ✅ Configure dynamic and static thresholds ✅ Regularly validate service membership ✅ Monitor alert volumes and patterns ✅ Adjust re-evaluation frequency as needed ✅ Leverage service groups for better organization Monitoring and Validation Regularly review service configurations Analyze alert trends and adjust thresholds Compare service-level metrics with individual resource performance Use reports and anomaly filters to refine the monitoring approach Conclusion LM Service Insights represents more than just a monitoring tool – it's a strategic approach to understanding and managing modern IT infrastructures wherever it resides. By shifting focus from individual resource metrics to service-level performance, organizations can better align their monitoring strategies with business objectives and service delivery goals. As IT environments continue to grow in complexity, the value of service-level monitoring becomes increasingly apparent. Service Insights provides the foundation for a more mature, strategic approach to infrastructure monitoring that can adapt and scale with your organization's needs. Remember that implementing Service Insights is a journey rather than a destination. Start with core services, learn from early implementations, and gradually expand coverage as you build confidence and expertise with the platform. Through continuous refinement and adaptation, Service Insights can become a cornerstone of your organization's monitoring strategy, enabling proactive management of service health and performance. Additional Resources Navigating the Service Insights Page Adding a Service Managing A Service Adding a Service Group Managing a Service Group Cloning A ServiceBest Practices For Practitioners: Dynamic Thresholds
The modern IT infrastructure consists of a complex ecosystem of interconnected systems spanning cloud and on-premises environments, generating unprecedented volumes of monitoring data. Static thresholds may not be intuitive enough to capture the nuanced performance characteristics of these dynamic environments due to the amount of incoming data, leading to alert fatigue, missed critical events, and inefficient resource allocation. Dynamic thresholds represent an evolutionary step in monitoring technology, leveraging advanced algorithms to create intelligent, adaptive monitoring strategies that distinguish between normal performance variations and genuine anomalies. Key Principles Dynamic thresholds transform monitoring by introducing adaptive mechanisms that intelligently interpret performance data. By analyzing historical performance data, these adaptive mechanisms move beyond rigid, predefined alert triggers, instead creating context-aware monitoring that understands the unique behavioral patterns of each monitored resource. This approach simultaneously addresses two critical challenges in modern IT operations: reducing unnecessary alert noise while ensuring that significant performance deviations are immediately identified and communicated. Recommended Implementation Strategies When to Use Dynamic Thresholds Recommended for: Metrics with varying performance patterns across instances Complex environments with diverse resource utilization Metrics where static thresholds are difficult to establish Not Recommended for: Status datapoints (up/down) Discrete value metrics (e.g., HTTP error codes) Metrics with consistently defined good/bad ranges Configuration Levels Global Level Best when most instances have different performance patterns Ideal for metrics like: CPU utilization Number of connections/requests Network latency Resource Group Level Useful for applying consistent dynamic thresholds across similar resources Cascades settings to all group instances Instance Level Perfect for experimenting or handling outlier instances Recommended when you want to: Reduce noise for specific instances Test dynamic thresholds on a limited subset of infrastructure Technical Considerations Minimum Training Data 5 hours required for initial configuration Up to 15 days of historical data used for refinement Detects daily and weekly trends Alert Configuration Configure to both trigger and suppress alerts Adjust advanced settings like: Percentage of anomalous values Band factor sensitivity Deviation direction (upper/lower/both) Pro Tip: Combining Static and Dynamic Thresholds Static and dynamic thresholds are not mutually exclusive—they can be powerful allies in your monitoring strategy. By implementing both: Use dynamic thresholds to reduce noise and catch subtle performance variations Maintain static thresholds for critical, well-defined alert conditions Create a multi-layered alerting approach that provides both granular insights and critical fail-safes Example: Dynamic thresholds for warning/error levels to adapt to performance variations Static thresholds for critical alerts to ensure immediate notification of severe issues Recommended Configuration Strategy Enable dynamic thresholds for warning/error severity levels Maintain static thresholds for critical alerts Use the "Value" comparison method when possible Best Practices Checklist ✅ Analyze existing alert trends before implementation ✅ Start with a small, representative subset of infrastructure ✅ Monitor and adjust threshold sensitivity ✅ Combine with static thresholds for comprehensive coverage ✅ Regularly review and refine dynamic threshold configurations Monitoring and Validation Utilize Alert Thresholds Report to track configuration Use Anomaly filter to review dynamic threshold-triggered alerts Compare alert volumes before and after implementation Conclusion Dynamic thresholds represent a paradigm shift in performance monitoring, bridging the gap between traditional alerting mechanisms and the complex, fluid nature of modern IT infrastructures. By leveraging machine learning and statistical analysis, these advanced monitoring techniques provide IT operations teams with a more nuanced, intelligent, and efficient approach to detecting and responding to performance anomalies. As IT environments continue to grow in complexity and scale, dynamic thresholds will become an essential tool for maintaining system reliability, optimizing resource utilization, and enabling proactive operational management. The true power of dynamic thresholds lies not just in their technological sophistication but in their ability to transform how organizations approach system monitoring—shifting from a culture of constant reaction to one of strategic, data-driven performance management. Additional Resources Enabling Dynamic ThresholdsBest Practices for Practitioners: Collector Installation and Configuration
Overview The LogicMonitor Collector is a Software as a Service (SaaS) that collects the data required for IT infrastructure monitoring in the LM Envision platform. Installed on Linux and/or Windows servers, it gathers performance metrics from selected devices across an organization's IT stack, whether it’s on-prem, off-prem, or in the cloud, using standard monitoring protocols. Unlike traditional monitoring approaches, a single Collector can monitor hundreds of devices without requiring individual agent installations on each resource. The Collector's core strength lies in its proprietary built-in intelligence that automatically recognizes device types and applies pre-configured Modules that define precise monitoring parameters specified to that device or platform. By encrypting collected data and transmitting it securely to LogicMonitor's servers via SSL, the Collector provides a flexible and centralized approach to infrastructure monitoring. This unique design allows organizations to strategically place Collectors within their network, enabling comprehensive performance visibility while minimizing monitoring overhead and complexity, with its monitoring capacity adapting to the device or service complex resources and specific metrics being collected. Key Principles LogicMonitor Collector deployment is guided by principles of efficiency, scalability, and intelligent monitoring: Centralized SaaS monitoring through strategic collector placement Simplified device discovery and metric collection Minimal performance impact on monitored resources Secure, encrypted data transmission Using the LogicMonitor Collector Recommended for: Complex IT infrastructures with multiple network segments Organizations requiring comprehensive, centralized monitoring Environments with diverse device types and monitoring requirements Not recommended for: Extremely small environments with few devices Networks with strict segmentation preventing central data collection Environments with severe network connectivity limitations Recommended Installation Best Practices Collector Placement and Sizing Install collectors close to or within the same network segments as monitored resources Choose servers that function as syslog or DNS servers for optimal placement Select the appropriate collector size based on the expected monitoring load Consider memory and system resources when sizing collectors Avoid monitoring resources across vast internet connections, firewalls, or through NAT gateways Keep in mind Windows collectors can monitor BOTH window and Linux devices while Linux collectors can only monitor Linux devices Recommended Disk Space New installation: ~500 MiB Logs: Up to 800 MiB Temporary files: <1500 MiB Report cache: <500 MiB NetFlow (if enabled): Up to 30 GiB Total recommended: <3.5 GiB (without NetFlow) Network and Security Configuration Ensure outgoing HTTPS (port 443) connectivity to LogicMonitor servers Configure unrestricted monitoring protocol (ex: SNMP, WMI, JDBC) Use proxy servers if direct internet connectivity is restricted Implement NTP synchronization for accurate time reporting Configure firewall rules to allow necessary collector communications Windows Collector Installation Recommended installation methods: Interactive Install Shield Wizard PowerShell silent installation Can be downloaded direct or bootstrap via CDN Service account considerations: For monitoring Windows systems in the same domain: Use domain account with local admin permissions For monitoring systems in different domains: Use local administrator account Ensure "Log on as a service" permissions are granted Linux Collector Installation Prerequisites: Bourne shell sudo package installed (for non-root installations) vim-common package (for xxd binary in newer versions) Recommended installation user: Default logicmonitor user Use executable permissions and install via binary Container Deployment Supported Kubernetes services: Microsoft Azure Kubernetes Service (AKS) Amazon Elastic Kubernetes Service (EKS) Google Kubernetes Service (GKS) Limitations: Full package installation only Linux-based collectors cannot monitor Windows WMI Performance and Optimization Monitor collector performance metrics regularly Tune collector size and configuration based on monitoring load Disable Standalone Script Engine (SSE) if memory is constrained Implement proper log and temporary file management Use container deployments for Kubernetes environments Best Practices Checklist ✅ Select strategically located servers for collector installation ✅ Choose the appropriate collector size based on expected monitoring load ✅ Configure reliable network connectivity and firewall rules ✅ Use non-root users for Linux collector installations ✅ Implement NTP time synchronization ✅ Monitor collector performance metrics ✅ Regularly update collectors to the latest stable versions ✅ Set collector “Down” notification chains for proper collector down alerting Monitoring and Validation Verify collector connection in LogicMonitor portal after installation Monitor collector CPU utilization, disk usage, and performance metrics Periodically review collector logs for potential issues Validate data collection accuracy and completeness Utilize and test collector failover and redundancy configurations Conclusion LogicMonitor Collectors provide a powerful, flexible approach to infrastructure monitoring, enabling organizations to gain comprehensive visibility with minimal operational overhead. By following best practices in placement, configuration, and ongoing management, IT teams can create a robust monitoring strategy that adapts to evolving infrastructure needs. Successful collector deployment requires careful planning, ongoing optimization, and a thorough understanding of your specific infrastructure requirements. Regularly reviewing and adjusting your monitoring approach will ensure continued effectiveness and performance. Additional Resources Collector Capacity Collector Versions Adding Collector Installing Collectors in Silent Mode Installing the Collector in a Container Configuring WinRM for Windows Collector agent.conf Collector Settings Collector Script Caching
