W3C home > Mailing lists > Public > public-lod@w3.org > February 2011

Re: The truth about SPARQL Endpoint availability

From: Christopher Gutteridge <cjg@ecs.soton.ac.uk>
Date: Mon, 28 Feb 2011 22:47:16 +0000
Message-ID: <EMEW3|8e75e99c83958a1f63a5f7ecdba709ddn1RMlP03cjg|ecs.soton.ac.uk|4D6C25F4.10005@ecs.soton.ac.uk>
To: Pierre-Yves Vandenbussche <py.vandenbussche@gmail.com>
CC: public-lod@w3.org, SW-forum <semantic-web@w3.org>, semanticweb@yahoogroups.com
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

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:31 UTC