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 <john@citylinkfiber.com> 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