fixed monitoring.properties, not using old moderator?action=listevents which is costly on big servers such as ARCHIVE

This commit is contained in:
Axel Uhl committed 2015-03-10 02:21:11 +01:00
1 parent 3d4aeb1904
commit ee16bd559d
8 files changed
+353 -353

No files matched your search

@@ -26,7 +26,7 @@ monitor.wait_after_failure = 60000
# - http://domain_or_address/path/to/check
# This format leads to a check that only succeeds if a status
# code of 200 is returned.
monitor.endpoints = http://127.0.0.1:8886/gwt/Leaderboard.html, http://127.0.0.1:8886/sailingserver/moderator?action=listevents, http://127.0.0.1:8886/events/ess40/index.html, http://127.0.0.1:8886/index.html
monitor.endpoints = http://127.0.0.1:8888/gwt/Home.html#WhatsNewPlace:navigationTab=SailingAnalytics, http://127.0.0.1:8888/sailingserver/api/v1/events, http://127.0.0.1:8888/events/ess40/index.html, http://127.0.0.1:8888/index.html
# bundle associated to endpoints
monitor.bundles = com.sap.sailing.gwt.ui, com.sap.sailing.server.gateway, com.sap.sailing.www.events, com.sap.sailing.www