Here are key places in the Grouper documentation and training with information on operational considerations:

You can monitor the health of the Grouper using the Grouper diagnostics URLs at http://{hostname}/grouper/status?diagnosticType=[trivial|db|all] for the Grouper UI, and http://{hostname}/grouperWS/status?diagnosticType=[trivial|db|all] for Grouper WS. If everything is ok, a 200 HTTP code will be returned, otherwise a 500 is returned with a description of the issue. The diagnostic URL has many options and is suitable for monitoring by systems like Nagios, Big Brother, etc. If you do not see the word SUCCESS on the “all” page, then something is wrong. Have monitoring tools like Nagios look for SUCCESS.

Use the Unresolvable Subject Deletion Utility (USDU) to clean up membership assignments for subjects that are no longer resolved by the Subject API.

Next: Conclusion

  • No labels