...
Grouper diagnostics provides a URL on Grouper WS and UI (in Grouper 2.2+) which will help to give the health of Grouper. This can include memory in the WS server, connection to the Grouper Registry DB, that sources can perform queries, and that Grouper loader jobs are successfully executing. If everything is ok, a 200 HTTP code will be returned, else 500. A description of the issue will be returned as well. The point is that this URL can by pointed to be web monitoring software like nagioNagios, big brotherBig Brother, BMC, etc.
There is general information displayed on success as well, the server name, number of WS requests (since server started), the last error (if recent), etc.
...
Code Block |
---|
SUCCESS loader_CHANGE_LOG_changeLogTempToChangeLog: Not checking, there was a success from before: 2016/01/31 15:14:50.000, expecting one in the last 30 minutes (31ms elapsed) SUCCESS loader_MAINTENANCE_cleanLogs: Loader job MAINTENANCE_cleanLogs ignored in config since URL param contains exclude which has 'loader_MAINTENANCE_cleanLogs' (31ms elapsed) SUCCESS loader_CHANGE_LOG_consumer_syncGroups: Loader job CHANGE_LOG_consumer_syncGroups ignored in config since URL param contains exclude which has 'loader_CHANGE_LOG_consumer_syncGroups' (31ms elapsed) SUCCESS loader_CHANGE_LOG_consumer_grouperRules: Not checking, there was a success from before: 2016/01/31 15:14:02.000, expecting one in the last 30 minutes (31ms elapsed) SUCCESS loader_SQL_SIMPLE__loader:owner__9178d7d636de49d6b271d12ca351dc19: Loader job SQL_SIMPLE__loader:owner__9178d7d636de49d6b271d12ca351dc19 ignored in config since URL param contains exclude which has 'loader_SQL_SIMPLE__loader:owner__9178d7d636de49d6b271d12ca351dc19' (31ms elapsed) |
Trivial option
Use this to do checks often, or when there is a cluster, you can use this on all nodes, and a deeper check on one node only
...
Code Block |
---|
<init-param> <param-name>findSubjectByIdOnCheckConfig</param-name> <param-value>true|false</param-value> </init-param> <init-param> <param-name>subjectIdToFindOnCheckConfig</param-name> <param-value>someSubjectIdWhichMightExistOrWhatever</param-value> </init-param> <init-param> <param-name>findSubjectByIdentifiedOnCheckConfig</param-name> <param-value>true|false</param-value> </init-param> <init-param> <param-name>subjectIdentifierToFindOnCheckConfig</param-name> <param-value>someSubjectIdentifierWhichMightExistOrWhatever</param-value> </init-param> <init-param> <param-name>findSubjectByStringOnCheckConfig</param-name> <param-value>true|false</param-value> </init-param> <init-param> <param-name>stringToFindOnCheckConfig</param-name> <param-value>someStringWhichMightExistOrWhatever</param-value> </init-param> |
https://url.to.grouper.edu/grouperWs/status?diagnosticType=sources
...
Code Block |
---|
HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.RuntimeException: There was an error in the diagnostic task DiagnosticLoaderJobTest, Loader job CHANGE_LOG_changeLogTempToChangeLog :Cant find a success since: 2010/05/17 01:38:50.000, expecting one in the last 30 minutes edu.internet2.middleware.grouper.ws.status.GrouperStatusServlet.doGet(GrouperStatusServlet.java:191) javax.servlet.http.HttpServlet.service(HttpServlet.java:617) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) root cause java.lang.RuntimeException: Cant find a success since: 2010/05/17 01:38:50.000, expecting one in the last 30 minutes edu.internet2.middleware.grouper.ws.status.DiagnosticLoaderJobTest.doTask(DiagnosticLoaderJobTest.java:103) edu.internet2.middleware.grouper.ws.status.DiagnosticTask.executeTask(DiagnosticTask.java:44) edu.internet2.middleware.grouper.ws.status.GrouperStatusServlet.doGet(GrouperStatusServlet.java:129) javax.servlet.http.HttpServlet.service(HttpServlet.java:617) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) note The full stack trace of the root cause is available in the Apache Tomcat/6.0.20 logs. |
If you dont want this protected by authentication
On the demo server, this URL is protected:
https://grouperdemo.internet2.edu/grouper_v2_3/status
Because this URL is protected:
https://grouperdemo.internet2.edu/grouper_v2_3
This server uses Apache in front of tomcat with reverse proxy AJP, so to make the status servlet not protected, make another mapping in apache which is not protected:
Code Block |
---|
ProxyPass /status_grouper_v2_3/status ajp://localhost:8131/grouper_v2_3/status |
that URL is not protected by authn, so it is unprotected:
https://grouperdemo.internet2.edu/status_grouper_v2_3/status?diagnosticType=all