I like the idea of creating logical representation of links on a map or page of some kind. Similar functionality in other platforms has been very helpful in the past in terms of information presentation, especially when showing things to executive management.
Also - being a logical representation of two ports that would presumably exist in the database somewhere, could logical link alarms be created and to reduce alert spam when a P2P circuit goes down?
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Adam Armstrong Sent: Tuesday, November 28, 2017 3:21 AM To: observium@observium.org Subject: Re: [Observium] Grouping both ends of Core P2P links into single Graph
What did you add to the other side? CoreB:?
Seems that humans could mess that system up. Humans are dumb.
adam.
Adam Armstrong
Managing Director & Lead Architect
Observium Limited
On 2017-11-28 08:52:23, Michael <obslist@smarsz.com mailto:obslist@smarsz.com > wrote:
We solved this by only adding the "Core:" prefix to one end of the link... Seems awfully agricultural in this conversation now.
The aggregated core graphs was the only purpose for us adding the tag though. We aren't leveraging it for any extra functions like alerting/matching.
HTH
Michael
On 28 Nov 2017, at 12:43 am, Andrew Lemin wrote:
Hi,
We are evaluating Observium at the moment, and we have many point-to-point links in our WAN as everyone should ;)
Each end of the same p2p link is labeled to be identical; interface Te1/1/1 description CORE:DeviceA=DeviceB
This results in two graphs in Observium. One for DeviceA (labelled “CORE:DeviceA=DeviceB”) and one for DeviceB (labelled “CORE:DeviceA=DeviceB”).
However as they are connected back-to-back to each other they show the exact same information (just “in” and “out” reversed obviously).
Is it possible to merge these two ports/graphs into a single logical Core link?
This would significantly save on screen real estate (halving the Core page at the least) and make tracing paths through the network much more logical.
Similar to how the Customer graphs aggregate multiple ports with the same description together. But I guess throwing away one side of the link maybe?
Details for each end could still be seen on the specific device’s page to view locally significant things like port errors etc
Thanks, Andy.
observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org mailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium