You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: instrumentation/jmx-metrics/library/jetty.md
+24-32Lines changed: 24 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,44 +10,36 @@ The metrics captured and their respective attributes depend on the Jetty version
10
10
11
11
Those metrics require the following Jetty modules to be enabled : `jmx`, `http`, `statistics`, `sessions` and at least one of `ee8-deploy`, `ee9-deploy` or `ee10-deploy`.
| jetty.thread.count | UpDownCounter || The current number of threads |
16
+
| jetty.thread.limit | UpDownCounter || The maximum number of threads in the pool |
17
+
| jetty.thread.busy.count | UpDownCounter || The current number of busy threads |
18
+
| jetty.thread.idle.count | UpDownCounter || The current number of idle threads |
19
+
| jetty.thread.queue.size | UpDownCounter || The current job queue size |
20
+
| jetty.io.select.count | Counter || The number of select calls |
21
+
| jetty.session.count | UpDownCounter | jetty.context | Current number of active sessions |
22
+
| jetty.session.count.max | Gauge | jetty.context| Maximum number of active sessions (*)|
23
23
24
24
-`jetty.context` corresponds to the deployed application subfolder in `webapps` folder.
25
-
-`jetty.selector.context` is a technical string identifier, high cardinality with values like `HTTP_1_1@7674f035` but stable per Jetty process instance
26
-
-`jetty.selector.id` is a technical numeric identifier, usually with low cardinality between `0` and `9`.
27
-
-`jetty.session.cache.id` is a technical numeric identifier, usually single `0` value is used
28
-
-`jetty.thread.context` is a technical string identifier, high cardinality with values like `Server@5a411614` but stable per Jetty process instance
29
-
-`jetty.thread.pool.id` is a technical numeric identifier, usually single `0` value is used
25
+
-`jetty.session.count.max` metric produces unpredictable values when more than one `org.eclipse.jetty.session:context=*,type=defaultsessioncache,id=*` MBean is present, the default Jetty deployment includes a single one.
30
26
31
27
## Jetty 9 to 11
32
28
33
29
Those metrics require the following Jetty modules to be enabled : `jmx`, `http` and `stats`.
| jetty.session.duration.max | Gauge | jetty.context | The maximum session duration |
42
+
| jetty.session.duration.mean | Gauge | jetty.context | The mean session duration |
47
43
48
44
-`jetty.context` corresponds to the deployed application subfolder in `webapps` folder.
49
-
-`jetty.selector.context` is a technical string identifier, high cardinality with values like `HTTP_1_1@7674f035` but stable per Jetty process instance
50
-
-`jetty.selector.id` is a technical numeric identifier, usually with low cardinality between `0` and `9`.
51
-
-`jetty.session.cache.id` is a technical numeric identifier, usually single `0` value is used
52
-
-`jetty.thread.pool.id` is a technical numeric identifier, usually single `0` value is used
53
-
-`jetty.session.handler.id` is a technical numeric identifier, usually single `0` value is used
45
+
-`jetty.session.duration.sum`, `jetty.session.duration.max`, `jetty.session.duration.mean` metrics will produce unpredictable results when more than one `org.eclipse.jetty.server.session:context=*,type=sessionhandler,id=*` MBean is present, the default Jetty deployment includes a single one.
0 commit comments