[ome-users] Testing an OMERO installation

[Chris MacLeod]

On Jul 5, 2012, at 9:18 AM, harri.jaalinoja at helsinki.fi wrote:
> Quoting "Chris MacLeod" <ckm at glencoesoftware.com>:
>> We verify the pieces starting with the database and move outward.  In our monitoring system we monitor postgres (as an application), then the OMERO database in specific (size, sessions, etc).  Then basic process checks on the OMERO side.  Is the java process running, are
> 
> 
> Hi Chris,
> 
> this sounds exactly like what we need. How do you implement this in practice? What monitoring system do you use? I don't know what they use in our IT department in general, but definitely it would be very useful to have our OMERO monitored in their standard way.
> 
> Would you be willing to share any scripts etc. where the checks you mentioned are implemented in practice? That way I wouldn't have to try (and possibly fail) to reinvent the wheel.
> 
> Regards,
> Harri

We use check_mk (http://mathias-kettner.de/checkmk.html) which is an add-on/front-end to nagios.

on the postgres side we use check_mk's postgres (http://mathias-kettner.de/checkmk_check_postgres_sessions.html, http://mathias-kettner.de/checkmk_check_postgres_stat_database.size.html) plugin which monitors database size as well as sessions and connections.

The login session code is basically what was in my previous message
  sudo -iu {omero_user} /path/to/bin/omero login -s localhost -u {username} -w {password} -t {timeout} 2>&1
by default omero allows a guest user (password guest) to login.  That code is then wrapped in whatever your monitoring system requires, check_mk / nagios look at the return code which omero login sets appropriately based on the result.

Hope that helps,

C