![](https://secure.gravatar.com/avatar/0fa97865a0e1ab36152b6b2299eedb49.jpg?s=120&d=mm&r=g)
Hi Matthias,
Storing this information would have too great an impact on the performance of the ports table, I think.
It would involve 4 extra fields in the ports table (it would be worthless to store "pps", as it would just be unicast+nonunicast).
To store this we'd need in/out counters and in/out rate. If we added this, you would be very unpopular with some of our larger installations... ;)
Are there really reasons to alert on non-unicast in the wild?
Thanks, Adam.
Adam.
Sent from BlueMail
On 15 Jul 2016, 20:51, at 20:51, Matthias Cramer matthias.cramer@iway.ch wrote:
Hi There
Is there a metric for normal packets per second and not only unicast packets (ifInUcastPkts_rate) and also a metric for non unicast packets per second. According to the doc at http://www.observium.org/docs/entities/#metrics_1 this is not existent... I would like to make an alert on high pps and if possible on high non unicast pps.
Any hint is appreciated.
Regards
Matthias
-- Matthias Cramer / mc322-ripe Senior Network & Security Engineer iway AG Phone +41 43 500 1111 Badenerstrasse 569 Fax +41 44 271 3535 CH-8048 Zurich http://www.iway.ch/ GnuPG 1024D/2D208250 = DBC6 65B6 7083 1029 781E 3959 B62F DF1C 2D20 8250 _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium