Forum Discussion

LMJBierman's avatar
Icon for Employee rankEmployee
2 years ago

Requirements for onboarding


Successful LogicMonitor implementations have these common traits: qualified & trained LM admins (i.e. power users), understanding of internal requirements, existing tool knowledge, and, above all, an awareness of dependencies that affect implementation velocity. 

Early awareness and completion of these dependency fulfillments will accelerate your LogicMonitor implementation and speed up time-to-value for your organization. Be sure to review this list and bring any questions to your Project Delivery team.

Compile Inventories

Device inventory 

  • Gather a full list of devices (IP addresses or DNS names) for import 
    • If you can’t obtain this, gather the subnets where your devices reside in order to build a NetScan policy

Cloud accounts 

  • If you plan to monitor cloud environments, configure roles, permissions, and credentials for your AWS, Azure, or GCP instance

Plan your groups carefully

Before importing devices or websites, map a device group and website group structure for your Resources tree (static or dynamic)

  • Confirm import approach: NetScan CSV or subnet policy 
    • Netscan CSVs make it easier to apply device-level properties and auto-populate your dynamic groups
  • Confirm the device group approach: Grouping structures

Obtain device credentials

Gather current, accurate credentials for any device you plan to import & monitor

  • Obtain SNMP (v2c or v3), WMI, NetApp, ESX, and other credentials - extracted from existing tools or gathered from your domain experts 
  • Review common credentials to understand what is supported in LogicMonitor and how to configure devices appropriately
    • Credentials can be applied as group-level properties so they can be appropriately inherited by sub-devices and sub-groups

Plan and provision dedicated Collectors

  • Deploy a Medium collector on a virtual or physical host in your environment
  • Ensure communication on TCP port 443
  • Ensure Collectors have network access to your devices 
    • If you have a secured internal network, consult your security team to allow the Collector to monitor devices on appropriate TCP/UDP ports
    • Partially or fully blocked ports will result in extra time required to resolve dead devices and troubleshoot missing data

Begin collecting dashboard and reporting requirements

Before allowing stakeholders to view dashboards and reports from LogicMonitor, you will need to identify:

  • Who is the audience that will view monitoring information?
  • What type of information do they need to view?
  • How detailed should the information be for the audience?
No RepliesBe the first to reply