Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > 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,493 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