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. Limit user access to a specific DCI?

Limit user access to a specific DCI?

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

    Hi!

    Sorry if this has already been covered in the forum, but I was unable to find it.

    Is there any way to limit the view for specific users, or groups, to a DCI or alarms?
    I am thinking about the same way to limit the view of an object.

    I have nodes with a lot of different DCI's and a lot of different users accessing the same server.
    The service desk group should see all the alarms, which they do today.
    But then I have a few other users that should only be able to see some of the alarms, for example if application A is down that will create a critical alarm, I would only want them to see that alarm.
    If application B goes down on the same node, I don't want them to see that alarm.

    It is possible to do it with another Netxms server instance and just forward the necessary alarms for those nodes to the "new" instance, but, it would be great if it was possible to do it in the same server. 🙂

    Best regards,
    Dan

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

      Hi!

      The only way I could think of is to create dummy nodes (with IP address of 0.0.0.0) for each DCI group, create DCIs on these nodes instead of main node, and set "proxy node" for DCIs to original node. Then you will be able to give access rights to individual dummy nodes, without giving any access to main node. This solution has some drawbacks - you either should create two DCIs - on main node and on dummy node, or you will not have common list of parameters on single node - only spread across multiple nodes.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • D
        D
        Dan
        wrote on last edited by
        #3

        Good morning!

        Hm ok, not sure what the best way is, but there are some positive things that come out of having an extra instance that can be separated from the live environment.
        I think that will be the way to go for me 🙂

        Thanks!

        Best regards,
        Dan

        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