Feature Request - Containers

[tmbutterworth]

Please implement a drillable containers feature. This would allow for grouping devices into containers with a container status for all devices in the container and being able to drill into containers. This would be useful for organizations with multiple graphically separated sites or multiple buildings on a campus to group devices based on location.

Please also add the ability to monitor the status of individual interfaces on routers, switches etc and create links to produce a host topology in the monitoring tab.

[cigamit]

Might be possible via sites, but its not something that I currently have time to implement. We certainly welcome Pull Requests though.

[tmbutterworth]

Thanks for the fast response. I'm not a php developer so I can't help with a pull request. Tim

…

On Sat, Jul 7, 2018 at 5:14 PM, Jimmy Conner ***@***.***> wrote: Might be possible via sites, but its not something that I currently have time to implement. We certainly welcome Pull Requests though. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#68 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEMC25eCrlnfROTYK8vU58Uhtepm7LSRks5uESSugaJpZM4VGeyV> .

[ghost]

Containers would be a great feature. Not sure if I need the drill-down capability, but with a container we could potentially build site dependencies that could suppress spurious or sympathetic alerts if the whole site was down. Unfortunately, I am also not a PHP developer, but I'm most certainly willing to look at the code for funsies.

[netniV]

We've broached the subject of device topology in another issue that's still open on here. It could be done but there are many safety checks that should be in place to ensure that an endless loop doesn't occur etc, which is why it has been left until a later milestone.

[ghost]

Cool. Just consider my comments an upvote for that feature then.

[cigamit]

One feature that I've been thinking of for some time is the concept of Device Groups. It's like a host or a node group, but with devices. Just a simple object that we can leverage elsewhere. @peektwice, check the Cacti issues list and if you don't see that feature enhancement, please log it. We can put it on the ever growing 1.3 feature list.

[netniV]

For alerting (more a thold issue but also encompasses monitor), I was thinking the simple answer there is to have a Parent type/ID. If it's type 1, it's a device. If it's type 2, it's a site, if it's type 3, it's a poller. You collect a table of alerts to be issued, then you suppress the alerts where a parent is also in alert status. The only snag is that the best way to achieve that is with a CTE which is MySQL 8 onwards:

https://stackoverflow.com/a/33737203/697159

[ghost]

Device group feature has already been logged as issue #2059. Looking forward to 1.3.

[TheWitness]

We currently have the Site and Location attributes for a device. That may be enough. This one has been opened for a while. You can tell I have not be messing with this plugin for quite a bit of time.