If you made a definition for it, it's new alerting. If you're not running a 2 year old install, it's new alerting. :D
What did the link in the email it sent you go to? (the edit link). You might be able to work out what happened from there.
adam. On 23/02/2015 03:42:03, John Brown john@citylinkfiber.com wrote: Not sure what delineates between old alerting and new alerting presently running
Observium 0.15.2.6286 (rolling)
no email generated for the alert.
On Sun, Feb 22, 2015 at 2:39 PM, Adam Armstrong wrote:
If it was the /old/ alerting, who knows, that stuff is broken.
If it's the /new/ alerting, there should be links in the email that'll give you a hint as to what it's talking about.
It's vaguely possible that there might be a bug in the code that works out what entity should be used.
adam.
On 23/02/2015 03:30:57, John Brown wrote:
38 some minutes ago, observium reported that BGP neigh 32.1.24.24 was down on our LAX router. yet this IP has never been configured on this router as anything, let alone a BGP neigh
A quick grep of rancid history for this router never shows this address.
Stumped..... _______________________________________________ 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
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium