Excellent suggestion. I seconded it... /gjs ----- Original Message ----- From: "Michael Shook" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 28, 2004 3:18 AM Subject: [SA-list] groups vs. dependencies
I was again looking at the big picture here with my SA hosts and seeing if I couldn't use grouping to assist in auto-html creation. Due to the fact that groups and dependancies don't get along together very well, I am unable to use groups at all because of the dependancies. This forces me to use custom ASP pages to group all the bits back together. So I was thinking, (STOP snickering...) since SA tracks the dependancies in a variable separate from the GroupID, why try to mush both into the same display window in the interface? Since dependancies represent the PHYSICAL layout of the network, and groups represent the LOGICAL layout of the network, why not have 2 different views? Dependancies are only used during a check cycle, and Groups are only used during output, so I can not see any interaction between the two variables EXCEPT those related to needing to display them both at the same time. Thus by having a dependancy view, I could be sure that I don't get 200 alerts when the primary router goes down, and by having a group view, I could get auto-html pages with logical grouping of devices. Just a thought for V5. Michael Shook Technical Analyst Saddle Creek Corporation 723 Joe Tamplin Industrial Blvd Macon GA 31217 478 742 8740 ext. 105 (work) 478 256 9318 (mobile) 478 742 7917 (fax) [EMAIL PROTECTED] http://www.saddlecrk.com --- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive --- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
