Thank you very much for the reply Kevin,
> Another option there is to make some kind of health check, and have
> openshift monitor it and alert/take the app down if something was
> unhealthy.
I have limited experience with OpenShift so I am not sure what is possible or not but I've been reading about health checks and the documentation always mentioned restarting the "unhealthy" container instead of sending an email notification. That wouldn't be helpful for me.
> There's currently no monitoring setup for communishift items.
> Once it's moved to staging / production, nagios checks can be added.
> Also, in our stg/prod clusters we have some simple monitoring like
> mailing you when a pod crashes or a build or cronjob fails.
Seems like the right course of action would be migrating to the production OpenShift instance. My questions regarding the migration process were answered in
https://pagure.io/fedora-infrastructure/issue/11814 so I will just have to prioritize that. Then I will get back to you in regards to the Nagios configuration.
Thank you again,