veyepar: Network Monitoring with AMP

Author(s):	Brendon Jones
Location	C2
Date	jan Thu 24	Days Raw Files
Start	14:25	First Raw Start	14:15
Duration	0:45:0	Offset	0:09:02
End	15:10	Last Raw End	15:10
Chapters	00:00 0:21:15
Total cuts_time	42 min.

https://2019.linux.conf.au/schedule/presentation/150/
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf Network_Monitoring_with_AMP.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

AMP is a distributed network monitoring platform designed to continuously perform active network measurements, capable of monitoring both network and service performance. Currently available tests include ICMP and TCP latency, UDP DNS latency, TCP throughput, HTTP performance and video streaming performance. Scheduled tests run continuously on the probes and report data to a central collector (or into your favourite storage/graphing tool) to generate graphs. The same tests can also be run as standalone tools from the command line as required.

There are AMP probes deployed at most universities in New Zealand, at major sites on the REANNZ network, and at many New Zealand Internet Service Providers, all with publicly available data. AMP is also being used internally by a number of ISPs to monitor customer experience and infrastructure performance.

This talk will cover the architecture and design of the AMP platform, as well as how the tests work, how the data gets reported and some of the issues we've encountered while trying to take accurate measurements. In particular it will show some of the challenges involved in creating a test to measure video streaming performance using a headless web browser. It will also explore some of the data that has been collected over the last few years and showcase some of the more impactful network events, misconfigurations, or generally interesting behaviour that has been observed.

Comment:

production notes