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
:summary: This guide explains how Java Flight Recorder (JFR) can be extended to provide additional insight into your Quarkus application.
10
+
:summary: This guide explains how JDK Flight Recorder (JFR) can be extended to provide additional insight into your Quarkus application.
11
11
:topics: observability,jfr
12
12
:extensions: io.quarkus:quarkus-jfr
13
13
14
-
This guide explains how https://openjdk.org/jeps/328[Java Flight Recorder] (JFR) can be extended to provide additional insight into your Quarkus application.
14
+
This guide explains how https://openjdk.org/jeps/328[Flight Recorder] can be extended to provide additional insight into your Quarkus application.
15
15
JFR records various information from the Java standard API and JVM as events.
16
16
By adding the Quarkus JFR extension, you can add custom Quarkus events to JFR. This will help you solve potential problems in your application.
17
17
@@ -99,7 +99,7 @@ We can launch the application with JFR configured to be enabled from the startup
This section is for those who would like to add new events to this extension.
332
+
This section is for extension authors who want to add new JFR events.
333
+
334
+
=== Depending on the API module
335
+
336
+
The Quarkus JFR extension separates the public API from the runtime implementation.
337
+
As a result, other extensions can implement JFR-based instrumentation by depending only on the JFR API module, without adding a dependency on the Quarkus JFR extension implementation itself.
338
+
339
+
At deployment time, an extension can detect whether the application has enabled the Quarkus JFR extension by using Quarkus capabilities:
0 commit comments