Groups to Worldmap

This feature made it to 11.5RC Thanks everyone for your vote!

Groups and being able to use my custom properties ie Lat and Long.. is pretty criitcal.  My users like maps and I love the look of the new maps but its needs to indicate status, location, and give me options like backgrounds overlays (ie weather map).  It would also be cool (maybe this is possible now) if when I added a map to the node view the map zoomed to the location of the node (of course I'd have to feed it the Lat Long coords).  I dont know if that is possible, but pretty cool.

Option 3

#3 Notify and Action

This would give ultimate flexibility in case you want to leave the existing node. I'm at a loss right now why you might want to leave the a duplicate node but part of the game in IT is planning for the unknown. You may not need the functionality today, but tomorrow it may be something needed or desired.

http://thwack.solarwinds.com/docs/DOC-172697

For me it would be ok, the information of "where the node/group is" must be put in the orion DB by us, the users, after all.

Sure, it would be easier to just associate an address (postal one) than gps coordinates, but I immagine that it could be difficult to implement and to standardize.

In both cases, for me it would be faster to populate some rows in the db than selecting, in the map, where each group/node should be

">LDave you still need to manually add the GPS Coordinates into the Custom Properties,for every node (or groups - If implemented),  is this OK ?

I would say that #2 and #3 are both good ideas.

With the simplicity of the table in the DB, it shouldn't be too hard to create a stored procedure on the back-end to remove the individual node if the user chooses 'remove' out of option 3. That would be ideal to me.

-ZackM

Loop1 Systems: SolarWinds Training and Professional Services

• LinkedIN: Loop1 Systems
• Facebook: Loop1 Systems
• Twitter: @Loop1Systems

You can create very granular maps by added one of these map objects to a groups and editing the map to default to the zoomed area.  The only problem is that that zoomed position does not show on the main map.  That is my points.  Would be nice for dynamically built maps based on Custom Properties and or grouping combined with addition custom properties.  You would not have to have nested groups to support the Long and Lat rather the map would have logic built in to look for a specified Long and Lat property at the node level.  If you did not use those properties you would still have to manually pick and place the nodes.

cliton1981,

I'm a big fan of using dynamic groups as much as possible (just wish they would perform well in the new web-reporting of 10.6). The only thing constant about IT is change, and dynamic groups help automate our day-to-day administrative tasks (like updating all the maps on each view). Just adding a new node to NPM, and based on the dynamic criteria rule we have configured, it is "magically" added to all the right groups; hence, automatically added to all the maps...pretty powerful stuff if you ask me.

As for your options above...groups are groups. If you have a group configured a certain way, then the nodes in that group are there regardless of where your group container is placed (Worldmap or NA). If a group container needs to be different for NA than for Worldmap, then we need to configure 2 groups and use them accordingly. Then again, nothing is telling us to use a group either. So, if a node is on the Worldmap by itself, and is located in a group...then that is what someone wants displayed, so they should co-exist.

It all comes back to how someone configured their groups and what they want to see. But I'm a huge fan of using dynamic groups as much as possible.

D