Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Network Performance Monitor (NPM) > Best practices for BGP Syslog alert

Best practices for BGP Syslog alert

Table of contents
Created by Malik Haider, last modified by MindTouch on Jun 23, 2016

Views: 2,135 Votes: 5 Revisions: 6


This article describes the best practices for BGP Syslog alert.


All NPM versions 


The best practice is to configure your router to send Syslog if the status changes. This enables you to not miss any state changed once you have the Syslog in Orion. In the Syslog viewer you can set up a rule for this specific Syslog. Then in the trigger actions tab, you can add an email action to be emailed when getting this Syslog.

If the neighbor description is in the message of the Syslog, then you should be able to put that in the email by the ${Message} variable. If it neighbor description is not in the message of the Syslog, then it would not be possible to add it in automatically and send it out.

Refer to the BGP Diagnostics section in the following article for more details:


Refer to the following article for the list of all variables that can be used with syslogs.



Other syslog variables


The following article give more information on the BGP Alerting available .

Last modified