Organizational Structure for Dynamic Groups

jeremyxmentzell

Happy Holidays Everyone!

I'm currently working on rolling out my first Orion implementation and I'm trying to keep everything as organized as possible but having a little difficulty.

I'm interested in knowing the community's thoughts or ideas about high-level organization for dynamic groups & placing groups on maps (specifically). Eg: Location - > Building(s) -> ? etc.

I can offer up that I'm grouping applications a bit differently than maybe defined by Orion so I'm trying to set up my groups as dynamic as possible with custom properties first but some of the one-offs will just be manual groups.

Any thoughts or ideas you might have on the organizational structure or other pitfalls that I should avoid would be most appreciated!n

aLTeReGo

It sounds like you're doing everything right as-is. The only thing you'll want ensure is that your groups include  granular items, and are not solely based on node groupings if you want the group status to accurately reflect the status of sub-components. For example, if you're monitoring SQL server running on server name [COLOSSUS], and the "Colossus" node is in a group called [SQL Servers]. If the SQL application goes down on Colossus the group status won't reflect this unless the SQL application is also added to the group "SQL Servers". The same is true for other items as well such as interfaces, volumes, etc.