Pro-active alerting - currently●Once a week look at logs

–last full day's blogs

●Email the technical contacts

●Relatively quick to implement

●Could be inaccurate

–No false alerts yet

–Looks at a single day only

–Data is ~ 12 hours old

●Delivered some results

–First alert went out to 58 eduroam members in December

–We are at around 30 alerts now

Purpose●eduroam is a federated system

●Everyone relies on everyone else

–Issues at one member's location can affect other organisation's users

–Adhere to the technical specification

–Further improve user experience

●Fix problems before they are tickets

Pro-active alerting - new portal●Near real time logging to database

–Working now on our dev server

–Perl script reading the log file

–Storing the variables only

●Enables:

–Dynamic, searchable logs through the browser

–Automated continuous error detection

–Real time reports/alerts in web interface

●More accurate periodic email alerting

Pro-active alerting – going further●All of the below planned for the web GUI

●No plans to increase email frequency

●Checks when saving new configurations

–SMTP email verification

–DNS lookups

–Status server testing

–More details in next session