We don't have much in the way of service-specific checks, but at least we can
make sure it's doing HTTPS and check for rate-limiting since that has come up.
Upstream Zulip has a bunch of stuff --
https://zulip.readthedocs.io/en/latest/production/troubleshooting.html#monitoring
-- that I should look into borrowing from eventually.
--- /dev/null
+define host {
+ use adehnert-host ; Name of host template to use
+ host_name zulip
+ address zulip.augsburg.vms.dehnerts.com
+}
+
+define service {
+ use adehnert-service
+ host_name zulip
+ service_description RUN-NGINX
+ check_command check_byssh_service!nginx.service
+}
+
+define service {
+ use adehnert-service
+ host_name zulip
+ service_description ZULIP-RATELIMIT
+ check_command check_byssh_generic!check_zulip_ratelimit
+ # Alerts will include a username, so don't send publicly
+ contact_groups adehnert-priv
+}
+
+define service {
+ use adehnert-service
+ host_name zulip
+ name zulip-https
+ service_description HTTPS
+ check_command check_https_hostname!-H zulip.dehnerts.com
+ __check_cert_expiry_days 10
+}