What we'll be wanting soon is a nagios check for our endpoints. Is there any established good/bad practice? Pierre-Yves Vandenbussche wrote: > Hello all, > > you have already encountered problems of SPARQL endpoint accessibility ? > you feel frustrated they are never available when you need them? > you develop an application using these services but wonder if it is > reliable? > > Here is a tool > <http://labs.mondeca.com/sparqlEndpointsStatus/index.html>[1] > that allows you to know public SPARQL endpoints availability > and monitor them in the last hours/days. > Stay informed of a particular (or all) endpoint status changes > through RSS feeds. > All availability information generated by this tool is accessible through a SPARQL > endpoint. > > This tool fetches public SPARQL endpoints from CKAN > <http://ckan.net/> open data. > From this list, it runs tests every hour for availability. > > [1] http://labs.mondeca.com/sparqlEndpointsStatus/index.html > [2] http://ckan.net/ > > Pierre-Yves Vandenbussche. -- Christopher Gutteridge -- http://id.ecs.soton.ac.uk/person/1248 You should read the ECS Web Team blog: http://blogs.ecs.soton.ac.uk/webteam/
Received on Monday, 28 February 2011 22:49:32 UTC