Grouper Users - Open Discussion List

[Chris Hyzer <>]

I use the status servlet which has been the WS for a while and is newly in 
the UI, hook that up to your monitoring/notification software (e.g. nagios) 
and you will know when something fails.  You see the change logs check for 
every 30 minutes, so you will know right away if the process dies.  Returns 
an HTTP 200 if ok, 500 if not.  Note, this is better than checking if the 
process is alive, maybe something else is wrong.  The status servlet will 
tell you for sure that jobs are successfully running since the last step is 
the log it in the database.

https://spaces.internet2.edu/display/Grouper/Grouper+diagnostics

e.g. 

https://someurl.for.ws.institution.edu/grouperWs/status?diagnosticType=all

Server: fastprod-medium-a-03, grouperVersion: 2.1.1, up since: 2015/06/07 
06:18, 68046 requests
SUCCESS memoryTest: Allocating 100000 bytes to an array to make sure not out 
of memory (36ms elapsed)
SUCCESS dbTest_grouper: Retrieved object from cache (36ms elapsed)
SUCCESS source_servPrinc: Source checked successfully recently (36ms elapsed)
SUCCESS source_g:gsa: Source checked successfully recently (36ms elapsed)
SUCCESS source_pennperson: Source checked successfully recently (36ms elapsed)
SUCCESS source_grouperExternal: Source checked successfully recently (36ms 
elapsed)
SUCCESS source_g:isa: Source checked successfully recently (36ms elapsed)
SUCCESS loader_CHANGE_LOG_changeLogTempToChangeLog: Not checking, there was a 
success from before: 2015/06/30 09:57:50.000, expecting one in the last 30 
minutes (36ms elapsed)
SUCCESS loader_MAINTENANCE__grouperReport: Not checking, there was a success 
from before: 2015/06/28 07:47:29.000, expecting one in the last 3120 minutes 
(36ms elapsed)
SUCCESS loader_MAINTENANCE_cleanLogs: Not checking, there was a success from 
before: 2015/06/29 06:00:31.000, expecting one in the last 3120 minutes (36ms 
elapsed)
SUCCESS loader_CHANGE_LOG_consumer_pcd: Not checking, there was a success 
from before: 2015/06/30 09:58:00.000, expecting one in the last 30 minutes 
(36ms elapsed)
SUCCESS loader_CHANGE_LOG_consumer_atlassian: Not checking, there was a 
success from before: 2015/06/30 09:58:00.000, expecting one in the last 30 
minutes (36ms elapsed)
SUCCESS loader_CHANGE_LOG_consumer_atlassianProd: Not checking, there was a 
success from before: 2015/06/30 09:58:00.000, expecting one in the last 30 
minutes (36ms elapsed)
SUCCESS loader_CHANGE_LOG_consumer_syncGroups: Not checking, there was a 
success from before: 2015/06/30 09:58:08.000, expecting one in the last 30 
minutes (36ms elapsed)
SUCCESS loader_CHANGE_LOG_consumer_grouperRules: Not checking, there was a 
success from before: 2015/06/30 09:58:10.000, expecting one in the last 30 
minutes (36ms elapsed)
SUCCESS 
loader_SQL_GROUP_LIST__penn:community:student:loader:crosslistGroups__2e207cde818b4106aaaa901d2d49a432:
 Not checking, there was a success from before: 2015/06/28 08:31:24.000, 
expecting one in the last 3120 minutes (37ms elapsed)
SUCCESS 
loader_SQL_SIMPLE__penn:community:facultyStudentStaff__ba018af2-4774-47fd-b831-cce3effe0e74:
 Not checking, there was a success from before: 2015/06/29 05:29:35.000, 
expecting one in the last 3120 minutes (37ms elapsed)
SUCCESS 
loader_SQL_SIMPLE__penn:community:employee__34ebb988-ce8b-4faa-94d9-b4760baaba1b:
 Not checking, there was a success from before: 2015/06/29 05:46:20.000, 
expecting one in the last 3120 minutes (37ms elapsed)
SUCCESS 
loader_SQL_SIMPLE__penn:library:apps:ezproxy:ezproxy__f1ba159f-2247-47f2-9ea2-9156f5e50dca:
 Not checking, there was a success from before: 2015/06/28 15:17:57.000, 
expecting one in the last 3120 minutes (37ms elapsed)
SUCCESS 
loader_SQL_SIMPLE__penn:community:employeeNonTemp__0970551c-b2f3-4b84-955d-23529fd35bf1:
 Not checking, there was a success from before: 2015/06/29 05:38:08.000, 
expecting one in the last 3120 minutes (37ms elapsed)
SUCCESS 
loader_SQL_SIMPLE__penn:sas:query:faculty:ft_lecturers__c8d884eb087d42b88142af7098b57371:
 Not checking, there was a success from before: 2015/06/28 08:12:02.000, 
expecting one in the last 3120 minutes (37ms elapsed)
SUCCESS 
loader_SQL_SIMPLE__penn:community:affiliate__361314eaa9df4e5dbec22190222218ff:
 Not checking, there was a success from before: 2015/06/29 05:04:30.000, 
expecting one in the last 3120 minutes (37ms elapsed)
SUCCESS 
loader_SQL_GROUP_LIST__penn:community:student:loader:studentPrimaryGroups__93750690c3474b41b349bbd196167d3e:
 Not checking, there was a success from before: 2015/06/28 08:05:11.000, 
expecting one in the last 3120 minutes (37ms elapsed)
SUCCESS 
loader_SQL_SIMPLE__penn:seas:school:staff__fc47182b-2e53-478c-9e87-550a53122b12:
 Not checking, there was a success from before: 2015/06/29 06:34:00.000, 
expecting one in the last 3120 minutes (37ms elapsed)
SUCCESS 
loader_SQL_SIMPLE__penn:sas:query:faculty:grad_stu_open_aps__2dbe91225ad84f1aaf4b0e59afe77fcd:
 Not checking, there was a success from before: 2015/06/28 08:13:02.000, 
expecting one in the last 3120 minutes (37ms elapsed)
SUCCESS 
loader_SQL_GROUP_LIST__penn:community:employee:centerRollupConfig__fbcb5bce80774747a74f750c70d20983:
 Not checking, there was a success from before: 2015/06/28 07:36:41.000, 
expecting one in the last 3120 minutes (38ms elapsed)
SUCCESS 
loader_SQL_SIMPLE__penn:community:alumni:law:lawAlumni__609e8abaa8bf4454919dd5ea8234bde2:
 Not checking, there was a success from before: 2015/06/29 06:23:57.000, 
expecting one in the last 3120 minutes (38ms elapsed)
....


-----Original Message-----
From: 

 
[mailto:]
 On Behalf Of Waldbieser, Carl
Sent: Tuesday, June 30, 2015 10:19 AM
To: grouper-users
Subject: [grouper-users] Monitoring of Grouper Loader?


I was wondering how others monitor their Grouper Loader process(es) to make 
sure that are staying up and running.
I had an issue not too long ago where the OS decided to terminate the loader 
process due to a low memory condition.  I wasn't aware this had happened 
until a couple days went by and our help desk received a call from an 
individual who could not get access to a system that was controlled via one 
of our reference groups.  Since the loader was not running, the reference 
group was not updated.

Thanks,
Carl Waldbieser
ITS Systems Programmer
Lafayette College