VO service monitoring

[John Taylor]

Hi all,
Yes, we also have a service that monitors VO services.  It's self- 
updating in that if your VOEvent brokers get harvested into our  
registry they ought to show up in the monitoring service shortly  
afterwards.  Are your brokers registered anywhere?  If so, send me  
the IVORNS and I'll make sure that we're picking them up.

Our VOMon publishes status reports on all IVOA services to:

http://thor.roe.ac.uk/vomon-full/status.xml

This particular report is intended for machine consumption and so  
lacks some of the data.  An example of a full report, restricted to  
showing WFAU services only, is at:

http://thor.roe.ac.uk/vomon/status.xml

John



On 27 Jul 2007, at 00:51, Alasdair Allan wrote:

>
> Rob Seaman wrote:
>> Has anybody considered how best to add our VOEvent brokers to this  
>> list:
>>
>> 	http://heasarc.gsfc.nasa.gov/vo/monitor
>>
>> This seems like an excellent way to raise VOEvent's visibility and  
>> to enforce some discipline on maintaining our services.  Vanilla  
>> TCP's "i am alive" packets are pretty much designed to support  
>> such monitoring already - seems like this should be an easy goal  
>> to meet.  Would just need a client that speaks vTCP on one side  
>> and whatever the monitor wants on the other.
>
> I actually do this as part of my network monitoring already, and  
> it'll show up for instance on the eSTAR status map at.
>
>   http://vo.astro.ex.ac.uk/estar/cgi-bin/status.cgi
>
> Oh, one of the telescope webcameras seems to have disappeared  
> behind an HTTP basic authentication wall (again), so just hit  
> "cancel" if it asks you for password. Got to fix that... *sigh*
>
> You don't even have to talk to the vTCP endpoint (although you  
> can), my event broker has a SOAP end point which you can ping. The  
> broker then does a self and sanity check, and returns a ACK or a  
> fault code. Shouldn't be too hard, AG in the UK do something  
> similar as well, I think John Taylor wrote it. I'm presuming there  
> is an IVOA note about this somewhere, but I haven't been paying  
> attention.
>
> Al.
>