- the pazpar2 log file don't contain an IP address
- the pazpar2 log file don't contain user names
- we don't know if the request comes from a client or a
  middle-layer software (Metaproxy, service-proxy)
- the log file format is mostly unstructured
- we need to map SRU requests with UDB to a connector name, MP-427

2 versions of reports
------------------------

a CSV file with:
a) by number of failures
b) by date

Examples
---------
here are the top errors from our pp2 production machine armada:

613 Error Connect failed from nysl.nysed.gov:2200/unicorn
613 Error Connect failed from library.emmawillard.org:2200/unicorn
613 Error Connect failed from 68.142.143.244:210/default
613 Error Connect failed from 141.222.2.14:7090/VOYAGER
503 Error Init rejected from 199.184.19.10:210/innopac
371 Search error Database unavailable (): sage.kohalibrary.com:210/sage_koha
371 Error Database unavailable from sage.kohalibrary.com:210/sage_koha
179 Error Truncated words too short from 66.194.176.40:210/innopac
179 Error Truncated words too short from 149.106.160.98:210/Innopac
179 Error Truncated words too short from 128.113.26.62:210/innopac
 90 Error Unspecified error from pac.hfmboces.org:210/horizon
 68 Error Timeout from nysl.nysed.gov:2200/unicorn
 68 Error Timeout from library.emmawillard.org:2200/unicorn
 68 Error Timeout from 68.142.143.244:210/default
 68 Error Timeout from 141.222.2.14:7090/VOYAGER
 53 Error Truncated words too short from 199.184.19.10:210/innopac
 34 Search error Unspecified error (Unable to retrieve data 0): pac.hfmboces.org:210/horizon
 32 Error Temporary system error from libms3.albany.edu:9991/ALB01
 22 Error Connection lost from connect.indexdata.com:9000/opinionarchives2?subdatabase=weekly_standard
 22 Error Connection lost from connect.indexdata.com:9000/opinionarchives2?subdatabase=american_spectator
 21 Search error Temporary system error (): libms3.albany.edu:9991/ALB01

the failed connect and error timeouts are hard errors, the site 
is down or behind a firewall.

I think we have to do it manually. We don't know from the pazpar2 log 
where the request comes from (IP address), or the user name in mkadmin. 
We have to login on mkadmin as global admin and check for the targets

