That entire bit of code needs rewritten, so I'll think about how it can be improved.
adam.
On 2014-04-22 15:35, Tim Calvin wrote:
Yes I am familiar with description parsing and use it heavily for customer names, circuit ID¹s, and AS numbers.
Seems to work fine for Customer ports but not for Peering ports which is why I sent an inquiry.
On 4/22/14, 3:17 PM, "Wouter Prins" wp@null0.nl wrote:
Hey Tim,
If you use the port descriptions as described here: http://www.observium.org/wiki/Interface_Description_Parsing it should work ok.
On 22 April 2014 21:44, Tim Calvin tcalvin@tlsn.net wrote: I was curious if there was a way to group together Peering ports in a way that it shows an aggregate graph similar to how Customer ports are handled.
On the customer ports page, I can see an aggregate graph of all a particular customers circuits. It seems all I have to do here is make sure they are named the same.
We have a few peering circuits to one entity and it would be nice to have that same behavior. I have them named the same but on the peering page the two circuits are shown individually with no aggregate totals.
Just wondering if there was some type of configurable option to enable this or not.
Let me know if I need to provide anymore info. Hopefully that makes sense.
Thanks,
Tim Calvin Texas Lone Star Network
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Wouter Prins wp@null0.nl _______________________________________________ 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