Discussion:
[smokeping-users] historical tracking of mtr/traceroute reports
Phillip Moore
2008-08-18 17:10:18 UTC
Permalink
Does anyone know of something existing that could be used to track
historically mtr/traceroute runs to correlate to badness seen in
smokeping? I have Smokeping monitoring connectivity between many
datacenters with master/slave. It proves helpful diagnosing problems
(often postmortem) and ruling the network in or out of the root cause
of a problem. Being able to see runs of mtr during the problem would
prove very helpful to netops though to see if there were routing
anomalies.

What I'd like to get (or create) is something that keeps a history of
the mtr/traceroute and be available for correlating to badness seen in
smokeping/FPing graphs. I thought I would check to see if anyone knew
of something existing before I go off on my own. I'll be the first to
admit I have no idea yet how this data would be represented in a UI
and integrated into smokeping UI.

Thanks for any suggestions.

Phillip Moore
-pdm
Peter Kristolaitis
2008-08-18 17:20:07 UTC
Permalink
The only thing I could think of offhand is to use alerts... you can use
the pipe syntax to run a script instead of sending an email when certain
conditions are met, and have that script run something akin to 'mtr
-rc', then save or email the results.

I can't think of an (easy) way offhand to integrate the results into the
SmokePing GUI, however.

- - Peter


Phillip Moore wrote:
| Does anyone know of something existing that could be used to track
| historically mtr/traceroute runs to correlate to badness seen in
| smokeping? I have Smokeping monitoring connectivity between many
| datacenters with master/slave. It proves helpful diagnosing problems
| (often postmortem) and ruling the network in or out of the root cause
| of a problem. Being able to see runs of mtr during the problem would
| prove very helpful to netops though to see if there were routing
| anomalies.
|
| What I'd like to get (or create) is something that keeps a history of
| the mtr/traceroute and be available for correlating to badness seen in
| smokeping/FPing graphs. I thought I would check to see if anyone knew
| of something existing before I go off on my own. I'll be the first to
| admit I have no idea yet how this data would be represented in a UI
| and integrated into smokeping UI.
|
| Thanks for any suggestions.
|
| Phillip Moore
| -pdm
|
| _______________________________________________
| smokeping-users mailing list
| smokeping-***@lists.oetiker.ch
| https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users


- --
Peter Kristolaitis
DBA / Code Monkey / General Geek

OpenPGP/GPG Key available from pgp.mit.edu

Key Fingerprint: 695D 7616 9903 6002 5756
~ D234 6E96 34B2 F974 14FE

Loading...