I find the groups system very useful.

We use it constantly for quickly getting to the items we want, which are already categorised by naming convention.

Thank you so much for your quick wins Adam :)



From: observium <observium-bounces@observium.org> on behalf of Adam Armstrong <adama@memetic.org>
Sent: 12 November 2014 22:15
To: Observium Network Observation System
Subject: Re: [Observium] Groups
 
The groups system exists simply because it was a relatively "quick win" by re-using the alerting system's association code. I'm not entirely sure what I would expect it to be used for. I didn't really get that far!
 
I had started adding group filtering abilities to the device and ports pages, which sort of does part of what you want, especially if it was expanded to other entity types.
 
Having fully customisable pages is still something I really have no idea how to do, but I think we *should* do, somehow.
 
adam.
 
------ Original Message ------
From: "Milton Ngan" <milton@valvesoftware.com>
To: "observium@observium.org" <observium@observium.org>
Sent: 11/11/2014 3:52:25 PM
Subject: [Observium] Groups
 
What is the intention of the groups feature? It seems like a really powerful way to group stuff together and have interesting views of things. But right now it just generates a list of entities that you can click through or hover over. I took a look at the code that generates all the various graph layouts (iftypes, health, ports). It seems that every page has its own code for handling the graph layout. It seem like this would be a great place to leverage a bunch of the existing code so you can create group specific views of sensors, ports etc... But it doesn't look like the code is structured that way (i.e reusable components/widgets). 

The standard views are good, but I want to be able to see them on a per datacenter/region basis rather than globally. The global view is visually interesting/pretty it is less useful.