Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. Easy way to monitor Services

Easy way to monitor Services

Scheduled Pinned Locked Moved Support
4 Posts 4 Posters 25.1k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T
    T
    theyareseven
    wrote on last edited by
    #1

    Is there an easy way to setup discovery (like with HDD for free space ect) on a node so the system will auto scan / check services, in an ideal world I would like the system to scan for all automatic services and add them, then the standard alerts if not running ect

    Thank you

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      Hi,

      most likely instance discovery for DCI creation should help (maybe with script a s a source).

      Best regards,
      Victor

      1 Reply Last reply
      0
      • T
        T
        Tursiops
        wrote on last edited by
        #3

        Hi,

        Without providing a full guide (the Admin Guide, Wiki and Forum should be able to help with the details), you could use a PowerShell script to generate an ExternalList. Something like this:

        $wmiServiceNames = (Get-WmiObject Win32_Service -Filter "StartMode='Auto'").Name
        foreach ($wmiServiceName in $wmiServiceNames) {
            $serviceDisplayName = (Get-Service $wmiServiceName).DisplayName
            $wmiServiceName + "," + $serviceDisplayName
        }
        

        Note, the above will provide a list of Service Names and Service Display Names, separated by commas.
        That way you can use instance discovery to split the two, then use DCI the parameter

        System.ServiceState{instance}
        

        while being able to use the more readable {instance-name} for the DCI description.

        Going a step further, you can create an event, action and event processing rule to automatically attempt to restart a service should it not be running.

        Cheers

        1 Reply Last reply
        0
        • D
          D
          dmna007
          wrote on last edited by
          #4

          i'm trying to do the exact same thing to make the dci creation process for services marked as 'auto start up' a less manual undertaking.  did you get anywhere with this?  if so some screenshots would be lovely to make my life easier!  thanks

          1 Reply Last reply
          0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          Powered by NodeBB Contributors
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Users
          • Groups