NikolayD

Members
  • Posts

    1
  • Joined

  • Last visited

Reputation

0 Neutral

About NikolayD

  • Rank
    Member
    Member
  1. Hey All, We have some use cases when we need to not only discover the instances by specific LM datasource - but also, create a separate device - which would be monitored separately as a standalone device. Ideally, we would prefer to have something similar to "cloud account" - where discovered cloud VMs would be monitored by LM collectors - if those discovered ones comply with some conditions (have some tags, located in specific resource group etc.) Those use cases, for example - SDWAN, OVMx86 monitoring - which are purely based on scripted methods for discovery, then, discovered instances are monitored via scripts as well (API based). At the same time, discovered instances has its own management IPs - representing remote vEdge (SDWAN), or OS - hosted by discovered hypervisor server or VM (OVMx86) - which are candidates for deeper monitoring (including usual methods available from LM - defining device type, and applying relevant data/event sources). Possible options would be: Netscan - using the same discovery script as for monitoring datasource, but, formatting the output - expected by netscan +: simple, out of box functionality (with minor efforts to adopt the discovery script) -: need to have multiple netscan configs for the same "technology" - by location, customer etc. no option to automatically deleting the devices in LM when they are not available anymore Creating devices as part of discovery script (LM API) +: full cycle to add/remove devices -: custom (efforts on developing/support), exposing LM API creds just curious: Does anyone have similar use cases and how they approached to implement it? Can be those monitoring solutions (like cloud account) - be developed and added as an option by LM customers? Does LM have something out of box to offer for those use cases (in current or future releases)? Regards, Nikolay