How is the Zenoss dashboard tree structure designed to work?  When running 
2.1.3 on a VM appliance, If I have locations similar to this:

/Locations
/Locations/Americas
/Locations/Americas/California
/Locations/Americas/New York
/Locations/Europe
/Locations/Europe/Finland
/Locations/Europe/UK

A base location of "/Locations" displays nothing.  Since its the root, I would 
expect it to display EVERYTHING.  In order to get all my sites in a single 
view, I have to structure (rather, unstructure) the locations like this:

/Locations
/Locations/Americas - California
/Locations/Americas - New York
/Locations/Europe - Finland
/Locations/Europe - UK

This operation seems to totally negate the purpose of having sub locations.  
What am I missing here?




-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=19226#19226

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to