What did you add to the other side? CoreB:?

On 2017-11-28 08:52:23, Michael <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
> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium