| ... |
... |
@@ -6,17
+6,16 @@ |
| 6 |
6 |
|
| 7 |
7 |
The beans are registered under the following names: |
| 8 |
8 |
|
|
9 |
+; Frontend-Server |
|
10 |
+: de.xima.fc:type=FSMonitor,qualifier=<contextName> |
|
11 |
+; Master-Server |
|
12 |
+: de.xima.fc:type=MSMonitor,qualifier=<contextName> |
| 9 |
9 |
|
| 10 |
|
-* {{litem title="{{fserver/~}~}"}}de.xima.fc:type=FSMonitor,qualifier=<contextName> {{/litem}} |
| 11 |
|
-* {{litem title="{{mserver/~}~}"}} de.xima.fc:type=MSMonitor,qualifier=<contextName> {{/litem}} |
| 12 |
|
- |
| 13 |
13 |
The context name is the context name of the applications. It is necessary for supporting parallel installations of {{formcycle/}} on a server. By default, the context name is the name of {{formcycle/}}'s WAR file, but it can be changed by [[modifying the context name parameter>>doc:Tomcat Einstellungen]]. |
| 14 |
14 |
|
| 15 |
15 |
When starting the server, the current context name is logged. You may need to modify the [[logging settings>>doc:LogginMenue]] to see the name. There are different monitoring attributes available for each bean, which are listed below. |
| 16 |
16 |
|
| 17 |
|
-=== {{mserver/}} (MSMonitor) === |
| 18 |
|
- |
| 19 |
|
-{{table caption="Overview of the settings for MSMonitor" dataTypeAlpha="0" preSort="0-asc"}} |
|
18 |
+{{table caption="Overview of the settings for MSMonitor (master server)" dataTypeAlpha="0" preSort="0-asc"}} |
| 20 |
20 |
|=Key|=Description|=Possible options |
| 21 |
21 |
|running|Whether the {{mserver/}} has been started successfully.|true ~| false |
| 22 |
22 |
|db_connected|Whether the {{mserver/}} could establish a connection to the database.| true ~| false |
| ... |
... |
@@ -27,17
+27,16 @@ |
| 27 |
27 |
|fs_connected_count|The number of {{fserver number="plural"/}} connected to this {{mserver/}}|A non-negative number. |
| 28 |
28 |
{{/table}} |
| 29 |
29 |
|
| 30 |
|
-=== {{fserver/}} (FSMonitor) === |
| 31 |
|
- |
| 32 |
|
-{{table caption="Overview of the settings for FSMonitor" dataTypeAlpha="0" preSort="0-asc"}} |
|
29 |
+{{table caption="Overview of the settings for FSMonitor (frontend server)" dataTypeAlpha="0" preSort="0-asc"}} |
| 33 |
33 |
|=Key|=Description|=Possible options |
| 34 |
34 |
|running|Whether the {{fserver/}} has been started successfully.|true ~| false |
| 35 |
35 |
|connected|Whether this {{fserver/}} is connected to a {{mserver/}}.|true ~| false |
| 36 |
36 |
|status|The connection status of this {{fserver/}}.|CONNECTED ~| NOT_CONNECTED ~| ERROR ~| RECONNECTING ~| DISCONNECTING ~| CONNECTING ~| AUTHENTICATING ~| WAIT_FOR_CONNECTION |
|
34 |
+{{/table}} |
| 37 |
37 |
|
| 38 |
38 |
== JSON REST API == |
| 39 |
39 |
|
| 40 |
|
-The monitoring beans can also be accessed via a JSON REST API. It can be accessed as follows: |
|
38 |
+The monitoring beans can also be accessed via a JSON REST API. This is done as follows: |
| 41 |
41 |
|
| 42 |
42 |
{{info}} |
| 43 |
43 |
http://localhost/formcycle/monitoring/read/de.xima.fc:type=MSMonitor,qualifier=formcycle |
| ... |
... |
@@ -105,7
+105,7 @@ |
| 105 |
105 |
|
| 106 |
106 |
{{panel title="Service definitions" fullwidth="true" initial="hidden" triggerable="true"}} |
| 107 |
107 |
Querying the number of {{fserver number="plurar"/}} not connected to this {{mserver/}}. When there are any disconnected servers, a warning will be displayed. When there is more than one disconnected server, Nagios will treat this warning as critical. |
| 108 |
|
- |
|
106 |
+<br> |
| 109 |
109 |
{{code}} |
| 110 |
110 |
define service{ |
| 111 |
111 |
use generic-service |