+/- based on a percentage or fixed number change from the last polled number? Factored by the delay count?
I have no idea how others would do it. I wouldn’t care if one or two routes changed, but if Verizon de-aggredated a /22 into /24s I’d like to know. Again.
From: Adam Armstrong Reply-To: Observium Network Observation System Date: Wednesday, April 15, 2015 at 8:22 AM To: Observium Network Observation System Subject: Re: [Observium] Alerting on BGP Ucast prefixes
Hah. A scalable way of remembering and using y number of previous measurements would be a good start!
It doesn't help that prefix data is held separate to session data, since not all sessions have all address families.
There are two possibilities, changing the bgp entity so that it also included prefix information from the other tables (slow), or adding per-afi bgp as an entity type to the alerting, which might be too cumbersome.
Also, how does one define the thresholds? -/+ a percentage based on the first seen? Still might get noisy.
We dislike implementing things which are likely to be suboptimal for any reason. Its better to get things right from the start.
Adam.
Sent with AquaMail for Android http://www.aqua-mail.com
On 15 April 2015 15:58:18 Michael Vieth <MVieth@nexatech.commailto:MVieth@nexatech.com> wrote: When reading the metrics and attributes wiki it seemed not possible. At least not with my toolset.
And agreed on the potential chattiness, I envisioned an alert where the if the # routes changed by more the x% of the y(time) average, then send an alert.
Cheers, Michael Vieth
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Pedersen, Sean Sent: Wednesday, April 15, 2015 9:52 AM To: Observium Network Observation System Subject: Re: [Observium] Alerting on BGP Ucast prefixes
The only BGP-related metrics at the moment are bgpPeerState, bgpPeerAdminStatus, and bgpFsmEstablishedTime.
The prefix data might be graphed, but the same data might not necessarily be available via the alerting system.
I’d like to see that kind of alerting as well! Though I don’t think it’d replace something more robust like BGPMon. Plus, it could get quite chatty unless you could set limits on route changes.
From: Michael Vieth Reply-To: Observium Network Observation System Date: Wednesday, April 15, 2015 at 7:48 AM To: Observium Network Observation System Subject: [Observium] Alerting on BGP Ucast prefixes
I am ecstatic that unicast prefix is graphed on Observium.
Is there a way to alert on a change in the number of routes being advertised?
For example, say I am receiving 500 routes from a peer, and that drops to 430, is that an alert-able event?
(Sorry if this is a repeated question, I am having difficulty finding detailed information on alerts outside of the wiki that just has general alerts documented.)
Cheers, Michael Vieth
Founded in 2007, IO provides the data center as a service to businesses and governments around the world.
The communication contained in this e-mail is confidential and is intended only for the named recipient(s) and may contain information that is privileged, proprietary, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. Please immediately notify the sender of the error, and delete this communication including any attached files from your system. Thank you for your cooperation. _______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Founded in 2007, IO provides the data center as a service to businesses and governments around the world.
The communication contained in this e-mail is confidential and is intended only for the named recipient(s) and may contain information that is privileged, proprietary, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. Please immediately notify the sender of the error, and delete this communication including any attached files from your system. Thank you for your cooperation.