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. Determining {instance} for DCI Some.Parameter.ScalarValue(*)

Determining {instance} for DCI Some.Parameter.ScalarValue(*)

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 9.0k 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.
  • H
    H
    Hospital
    wrote on last edited by
    #1

    Probably that's a stupid question, but I still don't understand what to specify for DCI {instance}. How to find out these instances? Talking about NetXMS_agent as origin.

    Okay, I understand FileSystem.FreePerc(/) or System.ServiceState(name_of_my_service).
    What should I put, for example in Hardware.Processor.Family(*) ?

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

      Unless you are looking for a very specific instance, you will want to use Instance Discovery.
      In which case you'd configure your DCI using something like FileSystem.FreePerc({instance}) and under Instance Discovery you'd select Agent List as Instance discovery method followed by entering FileSystem.MountPoints as List name.
      You can get a list of available agent lists by right-clicking on a node and selecting (I think) Info->Supported Lists. We've changed our menu structure, so not sure what the default is.
      For your Hardware.Processor.Family(*), I'd guess the list to use is "Hardware.Processors" (taken from the supported lists on one of my agents).

      The whole idea of Instance Discovery is that you don't need to enter every item manually. Nor do you have to worry about what happens when something changes, Instance Discovery runs regularly and will pick new items up and remove old ones (you can configure how long you want to keep the data once an item is no longer found).

      1 Reply Last reply
      0
      • H
        H
        Hospital
        wrote on last edited by
        #3

        Thank you for giving really good directions:

        @tursiops said in Determining {instance} for DCI Some.Parameter.ScalarValue(*):

        You can get a list of available agent lists by right-clicking on a node and selecting (I think) Info->Supported Lists.

        Bingo. Then followed by nxget utility and I finally see the instances:

        nxget -l my_host Hardware.Processors
        

        @tursiops said in Determining {instance} for DCI Some.Parameter.ScalarValue(*):

        you will want to use Instance Discovery.

        Yes, I completly agree. Just tested few simple things - it works!

        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