summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAzul <azul@riseup.net>2017-11-08 09:13:46 +0100
committerAzul <azul@riseup.net>2017-11-08 09:13:46 +0100
commit57faf66d7b82cc1ce67cf2e39ba7293c5a9d4bfa (patch)
tree8bd8c4d135dd15c27d971a775ddfecc89bd46844
parent71d10f85c5c9cc75dfb3f032a09877102833f739 (diff)
webapp: alert on 409 responses
They might be meaningful response codes for some scenarios. But so far we are not conciously sending them out. If they occur that is because we handed them down from couch. So we might want to fix the underlying issue. Couch 409s should be caught by the webapp and handled there.
-rw-r--r--puppet/modules/site_check_mk/files/agent/logwatch/webapp.cfg4
1 files changed, 4 insertions, 0 deletions
diff --git a/puppet/modules/site_check_mk/files/agent/logwatch/webapp.cfg b/puppet/modules/site_check_mk/files/agent/logwatch/webapp.cfg
index 337d9ec6..a5375cc8 100644
--- a/puppet/modules/site_check_mk/files/agent/logwatch/webapp.cfg
+++ b/puppet/modules/site_check_mk/files/agent/logwatch/webapp.cfg
@@ -1,6 +1,10 @@
/var/log/leap/webapp.log
# check for webapp errors
C Completed 500
+# also alert conflicts. They might be meaningful response codes
+# but so far we were just handing them on from couch and they
+# indicated some actual problem.
+ C Completed 409
# couch connection issues
C webapp.*Could not connect to couch database messages due to 401 Unauthorized: {"error":"unauthorized","reason":"You are not a server admin."}
# ignore RoutingErrors that rails throw when it can't handle a url