Advice on running reports interface in production setting
Hello The Galaxy reports interface (run_reports.sh) looks immensely useful for getting a handle on the usage of our local Galaxy, and I was wondering if anyone could offer advice on how they run the reports in a production environment. In terms of setting up and running the reports server, there doesn't appear to be much documentation however the instructions in the June 8th 2010 news brief covers the basics adequately: http://wiki.galaxyproject.org/DevNewsBriefs/2010%2006_08?highlight=%28report... This looks okay for running in an ad-hoc fashion (i.e. start it up, look at the reports in a browser running on localhost, shut it down again as required) but does anyone run it in a more persistent set-up? Or is ad-hoc the way to go? Any suggestions welcome, many thanks Best wishes, Peter -- Peter Briggs peter.briggs@manchester.ac.uk Bioinformatics Core Facility University of Manchester B.1083 Michael Smith Bldg Tel: (0161) 2751482
Hi Peter Why 'shut it down again'? Just keep it running all the time (on a different port than the actual Galaxy server, of course). And you have a real-time overview how busy the Galaxy server is, who is doing what, and (hopefully not) what errors occur. And at the end of the day or month you get your stats. Regards, Hans-Rudolf On 12/05/2012 12:04 PM, Peter Briggs wrote:
Hello
The Galaxy reports interface (run_reports.sh) looks immensely useful for getting a handle on the usage of our local Galaxy, and I was wondering if anyone could offer advice on how they run the reports in a production environment.
In terms of setting up and running the reports server, there doesn't appear to be much documentation however the instructions in the June 8th 2010 news brief covers the basics adequately:
http://wiki.galaxyproject.org/DevNewsBriefs/2010%2006_08?highlight=%28report...
This looks okay for running in an ad-hoc fashion (i.e. start it up, look at the reports in a browser running on localhost, shut it down again as required) but does anyone run it in a more persistent set-up? Or is ad-hoc the way to go?
Any suggestions welcome, many thanks
Best wishes, Peter
Hi Hans-Rudolf Thanks, that's a good point about "why shut it down again". Thanks for sharing your experience, Best wishes, Peter On 05/12/12 12:49, Hans-Rudolf Hotz wrote:
Hi Peter
Why 'shut it down again'? Just keep it running all the time (on a different port than the actual Galaxy server, of course).
And you have a real-time overview how busy the Galaxy server is, who is doing what, and (hopefully not) what errors occur. And at the end of the day or month you get your stats.
Regards, Hans-Rudolf
On 12/05/2012 12:04 PM, Peter Briggs wrote:
Hello
The Galaxy reports interface (run_reports.sh) looks immensely useful for getting a handle on the usage of our local Galaxy, and I was wondering if anyone could offer advice on how they run the reports in a production environment.
In terms of setting up and running the reports server, there doesn't appear to be much documentation however the instructions in the June 8th 2010 news brief covers the basics adequately:
http://wiki.galaxyproject.org/DevNewsBriefs/2010%2006_08?highlight=%28report...
This looks okay for running in an ad-hoc fashion (i.e. start it up, look at the reports in a browser running on localhost, shut it down again as required) but does anyone run it in a more persistent set-up? Or is ad-hoc the way to go?
Any suggestions welcome, many thanks
Best wishes, Peter
-- Peter Briggs peter.briggs@manchester.ac.uk Bioinformatics Core Facility University of Manchester B.1083 Michael Smith Bldg Tel: (0161) 2751482
participants (2)
-
Hans-Rudolf Hotz -
Peter Briggs