6 Replies Latest reply on Apr 14, 2008 11:11 AM by RogerWong

    Devices and Groups

    erharj
    erharj Feb 22, 2008 9:10 AM

      After my upgrade I am also trying to wrap my mind around the new organization of Devices and Groups in v9.


      I had many Groups in v8.5 that were simple, in that each Group included ONLY monitors for one computer, with a Dependency of a PING on that computer--and then that Group is part of an Email Alert.  Those did move into v9.


      However, when I create a new Device in v9, I can create it with multiple monitors for that Device or Computer similar to v8.5 Groups, with a Dependency of a PING--and add that to an Email Alert....So, what would be the difference between the two scenarios...A Group of monitors for a single device with a PING dependency, OR a Device of monitors with a PING dependency?  Do I even need to take that extra step in v9 to create a Group like I did in v8.5 in this scenario?  If not, then that leaves me with a mixture of configurations of Devices with no groups and my upgraded Devices WITH Groups from 8.5. ...Make sense?


      Thanks!

      • 4467 Views
      • Tags:
        • Re: Devices and Groups
          chris.lapoint
          chris.lapoint Feb 22, 2008 10:43 AM (in response to erharj)
          hen I create a new Device in v9, I can create it with multiple monitors for that Device or Computer similar to v8.5 Groups, with a Dependency of a PING--and add that to an Email Alert....So, what would be the difference between the two scenarios...A Group of monitors for a single device with a PING dependency, OR a Device of monitors with a PING dependency?
           

          They are essentially the same.  We wanted to formalize the concept of a device and its relationship with monitors and provide a container to store device-specific attributes from our improved discovery engine (e.g. L3 subnet, vendor, location, etc.).   So devices are really specialized groups whose members can only be monitors.   You can still create new groups and add *existing* monitors to them if you want.

          Do I even need to take that extra step in v9 to create a Group like I did in v8.5 in this scenario? 


          Nope.  That's the cool thing is that you can now use groups purely for logical organization of your devices (and take advantage of the newly added Groups within Groups feature).

           

          If not, then that leaves me with a mixture of configurations of Devices with no groups and my upgraded Devices WITH Groups from 8.5. ...Make sense?


          I think I hear you.  If you're saying that monitors with the same device/IP address in v8.5 were mapped to a device in v9, then you are correct.   In your particular scenario, you had groups = devices so during the upgrade there was a 1:1 correlation.
           

            • Re: Devices and Groups
              fauzan_azhary Feb 25, 2008 4:24 AM (in response to chris.lapoint)

              Hi clapoint,

               

              In your particular scenario, you had groups = devices so during the upgrade there was a 1:1 correlation.


              In v8.5 when we added new monitors using 'Add monitor', whatever the type of the monitor (SNMP, resource base, etc.), then as the result, in the "Monitor Name" field we can find the name format like "[IP ADDRESS] [MONITOR TYPE]".

              If then I don't want use [IP ADDRESS], so there's only [MONITOR TYPE] left on "Monitor Name" field, because the IP ADDRESS has already state on each the "Group Name" of the monitors, is there any unintended effect in the upgrading process to v9 ? Because as you state above, there will be an 1 : 1 correlation.

              Regards,

              Fauzan
               

                • Re: Devices and Groups
                  chris.lapoint
                  chris.lapoint Feb 25, 2008 8:23 AM (in response to fauzan_azhary)

                  The Monitor Name field "[IP ADDRESS] [MONITOR TYPE]" is used only as a label / friendly user name and does not have any effect in how we group monitors for the purposes of upgrade.   We create new device containers and name them based on your DNS configuration to map every monitor to a single device. 

                  Note, if you don't like where the monitors end up, you can contact support and they can help you move monitors between devices.

                    • Re: Devices and Groups
                      Capo Apr 14, 2008 4:03 AM (in response to chris.lapoint)

                      Note, if you don't like where the monitors end up, you can contact support and they can help you move monitors between devices.



                      Why is that?
                      I usualy use the Clone button to make similar monitors. Now they end up on the wrong device.
                      Please let me know how to change devices, and imo there must be a common way to do it.

                        • Re: Devices and Groups
                          chris.lapoint
                          chris.lapoint Apr 14, 2008 8:59 AM (in response to Capo)
                          Making monitors owned by devices is the first step toward monitor templates.  Instead of cloning, we'd like to give you the ability to create a monitor template and assign this to multiple devices and automatically pick up the required configuration attributes from the devices (e.g. IP address, hostname, etc.).

                          In the interim, here's how to move monitors from one device to another.   Go to Configuration Tab, select System Settings > Global Behavior Modifiers > Add and enter the following: 

                          Behavior modifier name:  monitors.orphan.enable

                          Behavior modifier value:  1

                          Now when you edit a monitor, you will see an option to move to orphaned group.   Once a monitor is in orphaned group, you can move to any device you like.

                          HTH,