Top Dependencies for LogicMonitor Enterprise Implementation

Dependencies Overview Successful LogicMonitor implementations have a few common customer traits: qualified and trained LM admins (“power users”), understanding of internal requirements, existing tool knowledge, anticipation of internal Change Management lead times, and awareness of dependencies that affect the speed of implementation. Prior to assessing how the technical dependencies below impact your implementation, review LogicMonitor … Continued

LogicMonitor Implementation Readiness Recommendations for Enterprise Customers

Readiness Overview In most large or complex IT environments, the idea of consolidating various performance monitoring tools across technology stacks and business units can seem like a daunting endeavor. In Professional Services, we guide hundreds of our largest customers through the implementation of our SaaS-based, hybrid monitoring platform. Our belief is that well-prepared and highly-engaged … Continued

Credentials for Accessing Remote Windows Computers

If the Collector is running as an account with rights to connect to the remote computers, no further credential modification is needed. If the account the credentials for the Collector service do not have access rights to remote computers you want to monitor, you can explicitly provide the credentials belonging to a user with administrative … Continued

Windows Server Monitoring and Principle of Least Privilege

Microsoft recommends Administrator group membership to ensure remote WMI functionality. However, you can run the remote WMI functionality without administrator privileges with some additional settings. This method works in most cases but not for all cases. Therefore, the assistance provided by your LogicMonitor support team may be limited and on a best-effort basis. You can … Continued

Why am I receiving account lock out alerts?

For WMI and Perfmon authentication, if you provide the credentials to log in to a domain machine using a local user account (a computer account), you can receive account lockout alerts. The collector tries to authenticate first against the domain. When that authentication fails, it attempts to authenticate locally. For example, if you provide Administrator as the account, you will receive domain alerts … Continued

Network scanning for additional devices

You can configure LogicMonitor collectors to periodically look for and automatically discover devices in your network. Automated discovery of devices in your network involves 3 steps: Creating a NetScan definition Running a NetScan on a particular collector Scheduling the NetScan to run on a collector or collectors as needed. When devices are discovered by a … Continued

Adding devices when they boot

You can use LogicMonitor’s REST API  to ensure that a device adds itself into monitoring upon startup. Providing the ability to self-register with your monitoring platform is essential when taking advantage of AWS, Azure, GCP, Rackspace, and other clouds services, in which devices are provisioned automatically in response to load.   See this page for … Continued

Defining authentication credentials

Using properties to set credentials LogicMonitor may require credentials (for example, JDBC passwords, SNMP community strings, SSH username, and so on) in order to collect data from your devices. You can use properties to set this information at the global, group, or device level. The level where you choose to set properties for your device may … Continued