[opennms-devel] Categories and other groupings
"Miskell, Craig" <[email protected]>
| Newsgroups | gmane.network.opennms.bugs |
|---|---|
| Message-ID | <[email protected]> |
Hi, I know there's been some (a lot?) of discussion over the past few years about categories, particularly with respect to the front page and the surveillance views. I've been pondering lately, and have an idea. 1) We should have one and only one type of "category" or "group" within OpenNMS; these groups can be used for a) The Web UI, including i) The front page ii) Dashboard iii) Surveillance view (is this the dashboard?) iv) Any future access control we might put in. v) Reporting b) Thresholds, Polling, Collecting, Capsd etc, being used to specify nodes for packages in each of these (i.e. replacing the "specific" and "include-range" type elements). c) Ummm, anything else? 2) These categories can be made up of a) Specific IPs b) IP ranges/IPLike expressions c) Specific *nodes* already in the database d) nodes by name/regex (matched at runtime) e) Other categories (nested categories) Item (c) in particular enables simple web-based manipulation of these categories, e.g. user goes to the node page of a newly discovered node, and uses some suitable UI to add this node to one or more existing groups. The web UI aspects of this lead to the potential to manipulate which thresholds apply to which nodes (rather than filtering at notification time, *after* the event has been generated and logged); similarly, data collection can be streamlined based on arbitrary categories. Being able to make groups of IP addresses (specific or expression) and also by adding individual nodes allows for the gamut of networks. What I mean is that on some networks, with 10K servers, you'd never add nodes to groups by hand, and you'd have some sensible IP scheme you can use to make your categories in big swathes. On other networks with 20-30 servers, IP schemes would be a PITA, and adding nodes by hand to one or more categories is the only sensible mechanism. I'm interested in making this happen (it'll take time though; it's pretty far reaching). Any thoughts or comments? Too big a chunk to chew? Craig Miskell, Technical Support, AgResearch Invermay 03 489-9279 Everything about the *nix culture points to not walking anywhere except possibly to a pub :-P ======================================================================= Attention: The information contained in this message and/or attachments from AgResearch Limited is intended only for the persons or entities to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipients is prohibited by AgResearch Limited. If you have received this message in error, please notify the sender immediately. ======================================================================= ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel