Skip to content

Commit e8bf831

Browse files
Add docs for JvmThreadDeadlockMetrics (#5614)
See #5222
1 parent ea173cc commit e8bf831

File tree

1 file changed

+2
-0
lines changed
  • docs/modules/ROOT/pages/reference

1 file changed

+2
-0
lines changed

docs/modules/ROOT/pages/reference/jvm.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,12 +10,14 @@ new JvmMemoryMetrics().bindTo(registry); <2>
1010
new JvmGcMetrics().bindTo(registry); <3>
1111
new ProcessorMetrics().bindTo(registry); <4>
1212
new JvmThreadMetrics().bindTo(registry); <5>
13+
new JvmThreadDeadlockMetrics().bindTo(registry); <6>
1314
----
1415
<1> Gauges loaded and unloaded classes.
1516
<2> Gauges buffer and memory pool utilization.
1617
<3> Gauges max and live data size, promotion and allocation rates, and the number of times the GC pauses (or concurrent phase time in the case of CMS).
1718
<4> Gauges current CPU total and load average.
1819
<5> Gauges thread peak, the number of daemon threads, and live threads.
20+
<6> Gauges the number of threads that are deadlocked.
1921

2022
Micrometer also provides a meter binder for `ExecutorService`. You can instrument your `ExecutorService`, as follows:
2123

0 commit comments

Comments
 (0)