Topic Options
#1689 - 07/06/06 02:50 AM Extension: Fire alert on route change
Pete Ness Offline



Registered: 08/30/99
Posts: 1106
Loc: Boise, Idaho
Extension Goal:

If you have a normally stable route and you'd like to know when the route changes, this extension will add an alert condition type that watches for route changes.

With today's relatively volatile routing system (internet routes change a lot), it may not be a great idea to use this on most routes. It's an interesting concept, though, that you may find useful.

The alert stays in "firing" mode as long as a route change has happened in the "Samples to examine" period. You can use this to your benefit to reduce the number of times you get notified about a route change.

Required PingPlotter Pro version

This extension requires PingPlotter Pro 3.10.0p or higher.

Installation Instructions
  • Download the attachment from this post (link near the title). The file will be named "Alert Condition - Route Change.ppx".
  • Save it in your "c:\Program Files\Pingplotter Pro\scripts" directory (or the appropriate path if you've not installed to that location).
  • Close and restart PingPlotter Pro.
  • Go to the alerts setup (Edit -> Alert Setup...)
  • Create a new alert, or select one of your existing alerts you want to test this on.
  • In the "Method" dropdown, select "When route changes"
  • Continue to configure the alert, per your needs.
  • Make sure this alert is tied to a target in your route. The best bet is to tie it to the final destination you want to be alert on. You can also tie it to intermediate route, but if the route changes where the intermediate hop is no longer participating in the route, you won't be alerted until it starts participating again.
Wrap up

If you find any issues are problems, please post a message here or send an email to support@pingplotter.com.


Attachments
Alert Condition - Route Change.ppx (343 downloads)



Edited by Pete Ness (08/17/12 12:32 AM)
Edit Reason: Fixed so route change alert doesn't happen on first sample.

Top
#2256 - 02/09/11 06:52 AM Re: Extension: Fire alert on route change [Re: Pete Ness]
Mara Offline


Registered: 02/09/11
Posts: 1
Hello Pete

I am using this extension to monitor route changes inside my network and email alerts whenever they happen.

I was just wondering if it's possible to include current route and previous route to email body? I can only see ##HISTORYDATA## attribute which is showing the current route.

I can of course use the ##ATTACHMENT## and ##SCREENSHOT## attributes but it would be easier to read it from the email body.

example:

A PingPlotter Pro alert has fired for the following period(s):
9.2.2011 13:19:48 to Current

Tracing to: www.google.fi 209.85.149.99
Monitoring: ber01s02-in-f99.1e100.net 209.85.149.99

Route was:
Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.2.1 --------------
3 192.168.3.1 --------------
4 209.85.149.99 ber01s02-in-f99.1e100.net

Route is now:
Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.2.1 --------------
3 192.168.5.1 --------------
4 209.85.149.99 ber01s02-in-f99.1e100.net

Thanks

Mara



Top
#2273 - 03/21/11 12:53 PM Re: Extension: Fire alert on route change [Re: Mara]
Pete Ness Offline



Registered: 08/30/99
Posts: 1106
Loc: Boise, Idaho
Sorry, there's no current way to show the two different routes at present.

It *might* be possible to do this with a custom alert event type, though, that uses a 100% scripted email event. Contact us via email to talk about some ideas here.

Top
#2923 - 09/25/16 10:39 PM Re: Extension: Fire alert on route change [Re: Mara]
Kamoteman Offline


Registered: 09/25/16
Posts: 1
Originally Posted By: Mara
Hello Pete

I am using this extension to monitor route changes inside my network and email alerts whenever they happen.

I was just wondering if it's possible to include current route and previous route to email body? I can only see ##HISTORYDATA## attribute which is showing the current route.

I can of course use the ##ATTACHMENT## and ##SCREENSHOT## attributes but it would be easier to read it from the email body.

example:

A PingPlotter Pro alert has fired for the following period(s):
9.2.2011 13:19:48 to Current

Tracing to: www.google.fi 209.85.149.99
Monitoring: ber01s02-in-f99.1e100.net 209.85.149.99

Route was:
Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.2.1 --------------
3 192.168.3.1 --------------
4 209.85.149.99 ber01s02-in-f99.1e100.net

Route is now:
Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.2.1 --------------
3 192.168.5.1 --------------
4 209.85.149.99 ber01s02-in-f99.1e100.net

Thanks

Mara





Worth to have one. vote to have this on future releases

Top

Search

Who's Online
0 registered (), 9 Guests and 1 Spider online.
Key: Admin, Global Mod, Mod