I'll post an example of the same device being twice in the database. It happens a lot with Isilon when monitoring all cluster nodes individually as each node can have multiple IPs and these IPs are not constant.
On the group topic, my thought was to keep the current device/port approach, but allow to associate each group with a user defined (or somewhat customizable) parent group so one an create a hierachy and not have all groups map directly to the top. I've tried to use naming conventions (see screenshot) to do this at one level, but it doesn't really solve the problem when having 30+ groups. If there were a group level hierarchy built into the UI & database similar to what is done for geographical location, one could have many groups without it looking messy and basically create top level groups based upon technology/customers/project/data center etc.
[image: Screen Shot 2016-12-20 at 8.52.34 AM.jpg]
/Jesper On Mon, Dec 19, 2016 at 19:32 Adam Armstrong adama@memetic.org wrote:
Hi Jesper,
If things are being added with the same sysname/snmp engine id, that's a bug that needs sorted out. We shouldn't need a manual list :)
For sub groups, how exactly would that work? how would you put things into subgroups, and how would the UI handle it? Do you still want to be able to see the entirety of the parent group?
adam.
On 02/12/2016 23:41:02, Jesper Frank Nemholt jfn@dassic.com wrote: Hi!
1. Especially with autodiscovery I get the same devices created multiple times as the hostname differ and Observium don't seem to always properly identify that the sysName and SNMP ID is the same.
What I end up with is either the same device being in there twice. I also have this issue on some solutions using clustering and internal DNS & DHCP so nodes can have multiple IPs and DNS names and change these over time so the only constant is SNMP sysName and SNMP ID.
What I am doing now as a workaround is to disable all but one entry per device when I see these duplicates, but it would be great to either have a better check to avoid this from the very beginning, or potentially to have something like what is present for syslog host mapping to allow a N to 1 mapping of devices like :
$config['device']['host_map']['foo.bar'] = 'bar.foo'; // device hostname/sysname $config['device']['host_map']['foo.bar'] = 'foo.foo'; // device hostname/sysname
With something like this in config.php I could then delete the duplicate entries and they would not be auto discovered again, and I'd avoid having to disable them.
2. The other thing is that it would be great if it was possible to create subgroups for devices, ports and custom OIDs. When having lots of groups for different areas or lots of custom OIDs it quickly gets crowded and having the ability to organize these in a group hierachy would be great, similar to how locations are grouped by country when using geo-coding.
/Jesper
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
