From 8bc1e6372e159abe2b630e1dce5b60f0464588dc Mon Sep 17 00:00:00 2001 From: Andrew Azores Date: Fri, 7 Feb 2025 15:49:09 -0500 Subject: [PATCH 01/11] docs(quickstart): update links --- config/openshift/cryostat-quickstart.yaml | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/config/openshift/cryostat-quickstart.yaml b/config/openshift/cryostat-quickstart.yaml index 679518870..6d51499fc 100644 --- a/config/openshift/cryostat-quickstart.yaml +++ b/config/openshift/cryostat-quickstart.yaml @@ -43,14 +43,13 @@ spec: -Dcom.sun.management.jmxremote.ssl=false ``` - Note: This method enables remote JMX without authentication. For details on configuring authentication with SSL/TLS for Remote JMX, see [Configuring Java applications](https://access.redhat.com/documentation/en-us/red_hat_build_of_cryostat/2/html/getting_started_with_cryostat/assembly_configuing-java-applications_cryostat). + Note: This method enables remote JMX without authentication. For details on configuring authentication with SSL/TLS for Remote JMX, see [Configuring Java applications](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications). 1. Click **Save.** title: Enable **Remote Java Management Extensions (JMX) connections** on your Java Application review: failedTaskHelp: >- - This task isn't verified yet. Try the task again, or [read - more](https://access.redhat.com/documentation/en-us/red_hat_build_of_cryostat/2/html/getting_started_with_cryostat/assembly_configuing-java-applications_cryostat) + This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications) about this topic. instructions: > #### Click **Reload** at the bottom of the **Environment** tab. @@ -79,8 +78,7 @@ spec: title: Updating Red Hat OpenShift Service with the remote JMX port review: failedTaskHelp: >- - This task isn't verified yet. Try the task again, or [read - more](https://access.redhat.com/documentation/en-us/red_hat_build_of_cryostat/2/html/getting_started_with_cryostat/assembly_configuing-java-applications_cryostat) + This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications) about this topic. instructions: > #### Verify that the service port is added to the sample resource: @@ -114,12 +112,11 @@ spec: title: View your Java Application as a target in Cryostat review: failedTaskHelp: >- - This task isn't verified yet. Try the task again, or [read - more](https://access.redhat.com/documentation/en-us/red_hat_build_of_cryostat/2/html/getting_started_with_cryostat/assembly_configuing-java-applications_cryostat) + This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications) about this topic. instructions: |- #### Verify your Java application is running on Red Hat build of Cryostat web application: Did the Cryostat web application open in a separate browser window? conclusion: >- - Your Java application has now been configured to be detected by Cryostat. To profile your Java applications with Cryostat, please follow [this documentation](https://access.redhat.com/documentation/en-us/red_hat_build_of_cryostat/2/html/getting_started_with_cryostat/assembly_creating-recordings_assembly_configuing-java-applications). + Your Java application has now been configured to be detected by Cryostat. To profile your Java applications with Cryostat, please follow [this documentation](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/using_cryostat_to_manage_a_jfr_recording/index). From 291b9e2381f8dfb0a5fe36872394476bd5b53b1e Mon Sep 17 00:00:00 2001 From: Andrew Azores Date: Fri, 7 Feb 2025 15:54:29 -0500 Subject: [PATCH 02/11] put title before description --- config/openshift/cryostat-quickstart.yaml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/config/openshift/cryostat-quickstart.yaml b/config/openshift/cryostat-quickstart.yaml index 6d51499fc..0e9de3131 100644 --- a/config/openshift/cryostat-quickstart.yaml +++ b/config/openshift/cryostat-quickstart.yaml @@ -23,7 +23,8 @@ spec: - **Note**: The quickstart uses a sample [Quarkus application](https://github.com/quarkusio/quarkus-quickstarts). You can deploy your own Quarkus application or follow the **Get started with Quarkus using s2i** quick start. tasks: - - description: > + - title: Enable **Remote Java Management Extensions (JMX) connections** on your Java Application + description: > To enable remote JMX connections: 1. In the main navigation, click the dropdown menu and select **Administrator**. @@ -46,7 +47,6 @@ spec: Note: This method enables remote JMX without authentication. For details on configuring authentication with SSL/TLS for Remote JMX, see [Configuring Java applications](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications). 1. Click **Save.** - title: Enable **Remote Java Management Extensions (JMX) connections** on your Java Application review: failedTaskHelp: >- This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications) @@ -55,7 +55,8 @@ spec: #### Click **Reload** at the bottom of the **Environment** tab. Do you see a **single values entry** for **`JAVA_OPTS_APPEND`**? - - description: > + - title: Updating Red Hat OpenShift Service with the remote JMX port + description: > To update Red Hat OpenShift Service with the remote JMX port: 1. In the main navigation, click the dropdown menu and select **Administrator**. @@ -75,7 +76,6 @@ spec: ``` 1. Click **Save**. - title: Updating Red Hat OpenShift Service with the remote JMX port review: failedTaskHelp: >- This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications) @@ -93,7 +93,8 @@ spec: Do you see **Service port: jfr-jmx -> Pod port: 9091** in the quarkus-quickstarts service? - - description: > + - title: View your Java Application as a target in Cryostat + description: > View your Java application as a target in the Red Hat build of Cryostat web application: 1. In the main navigation, click the dropdown menu and select **Developer**. @@ -109,7 +110,6 @@ spec: 1. In the web application, click **Recordings** in the navigation menu. 1. View quarkus-quickstarts (or your deployed application) in the **Targets** list. - title: View your Java Application as a target in Cryostat review: failedTaskHelp: >- This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications) From a6db80c953fb9f493afe1097ceefb702377fbebe Mon Sep 17 00:00:00 2001 From: Andrew Azores Date: Fri, 7 Feb 2025 15:54:38 -0500 Subject: [PATCH 03/11] update text --- config/openshift/cryostat-quickstart.yaml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/config/openshift/cryostat-quickstart.yaml b/config/openshift/cryostat-quickstart.yaml index 0e9de3131..ed60ff441 100644 --- a/config/openshift/cryostat-quickstart.yaml +++ b/config/openshift/cryostat-quickstart.yaml @@ -15,13 +15,13 @@ spec: - To enable Cryostat to gather, store, and analyze Java Flight Recorder (JFR) data about target applications that run on Java Virtual Machine (JVM)s, you must configure the applications so that Cryostat can detect and connect to them. - - This requires you to configure your Java applications to allow Java Management Extensions (JMX) connections and use an OpenShift Service for detection and JMX for connectivity. + - You can use Red Hat build of Cryostat Operator to automatically configure your target application to use the Cryostat Agent to register with a specific Cryostat instance and provide HTTP-based connectivity. - - JMX is a standard feature on a JVM with which you can monitor and manage target applications that run on the JVM. You must enable and configure JMX when you start the JVM because Red Hat build of Cryostat requires the target applications to expose a JMX port, so that it can communicate with the target applications over this JMX port. Red Hat build of Cryostat starts and stops the JFR recordings and pulls the JFR data over the network, enabling it to store and analyze this JFR data. + - Alternatively, you can configure your Java applications to allow Java Management Extensions (JMX) connections and use an OpenShift Service for detection and JMX for connectivity. JMX is a standard feature on a JVM with which you can monitor and manage target applications that run on the JVM. You may enable and configure JMX when you start the target application JVM so that Red Hat build of Cryostat can communicate with your JVM over the network using built-in JDK functionality. - - If you have not yet installed the Red Hat Build of Cryostat operator, start with the **Get started with the Red Hat build of Cryostat** quick start. + - If you have not yet installed the Red Hat Build of Cryostat Operator, start with the **Get started with the Red Hat build of Cryostat** quick start. - - **Note**: The quickstart uses a sample [Quarkus application](https://github.com/quarkusio/quarkus-quickstarts). You can deploy your own Quarkus application or follow the **Get started with Quarkus using s2i** quick start. + - **Note**: The quickstart uses a sample [Quarkus application](https://github.com/quarkusio/quarkus-quickstarts). You can deploy your own application or follow the **Get started with Quarkus using s2i** quick start. tasks: - title: Enable **Remote Java Management Extensions (JMX) connections** on your Java Application description: > From cb7ba7c3b480904a57ba4a2cb61101d7c919309f Mon Sep 17 00:00:00 2001 From: Andrew Azores Date: Fri, 7 Feb 2025 16:08:08 -0500 Subject: [PATCH 04/11] rename --- ...-quickstart.yaml => cryostat-quickstart-jmx.yaml} | 12 ++++++------ config/openshift/kustomization.yaml | 2 +- 2 files changed, 7 insertions(+), 7 deletions(-) rename config/openshift/{cryostat-quickstart.yaml => cryostat-quickstart-jmx.yaml} (95%) diff --git a/config/openshift/cryostat-quickstart.yaml b/config/openshift/cryostat-quickstart-jmx.yaml similarity index 95% rename from config/openshift/cryostat-quickstart.yaml rename to config/openshift/cryostat-quickstart-jmx.yaml index ed60ff441..49427df37 100644 --- a/config/openshift/cryostat-quickstart.yaml +++ b/config/openshift/cryostat-quickstart-jmx.yaml @@ -1,23 +1,23 @@ apiVersion: console.openshift.io/v1 kind: ConsoleQuickStart metadata: - annotations: + annotations: capability.openshift.io/name: Console - name: configuring-cryostat + name: configuring-cryostat-jmx spec: icon: >- data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz48c3ZnIGlkPSJMYXllcl8xIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAxMDI0IDEwMjQiPjxkZWZzPjxzdHlsZT4uY2xzLTF7ZmlsbDojZmZmO30uY2xzLTJ7ZmlsbDojMWI0OTY1O30uY2xzLTN7ZmlsbDojOTVjOWU5O30uY2xzLTR7ZmlsbDojNWZhOGQzO308L3N0eWxlPjwvZGVmcz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iNjYxLjc2IDEzOS40OSA2MDcuMzggODUuMTEgNTUwLjQ1IDE0Mi4wNCA1NTAuNDUgMCA0NzMuNTUgMCA0NzMuNTUgMTQyLjA0IDQxNi42MiA4NS4xMSAzNjIuMjQgMTM5LjQ5IDUxMiAyODkuMjYgNjYxLjc2IDEzOS40OSIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMiIgcG9pbnRzPSI1OTcuMzQgNjU5LjgyIDY5OC45MiA2ODcuMDQgNjc3LjY0IDYwNy42MyA3NTcuMDQgNTg2LjM1IDY4Mi42OSA1MTIgNzU3LjA0IDQzNy42NSA2NzcuNjQgNDE2LjM3IDY5OC45MSAzMzYuOTYgNTk3LjM0IDM2NC4xOCA1NzAuMTMgMjYyLjYxIDUxMiAzMjAuNzQgNDUzLjg3IDI2Mi42MSA0MjYuNjYgMzY0LjE4IDMyNS4wOSAzMzYuOTYgMzQ2LjM2IDQxNi4zNyAyNjYuOTYgNDM3LjY1IDM0MS4zMSA1MTIgMjY2Ljk2IDU4Ni4zNSAzNDYuMzYgNjA3LjYzIDMyNS4wOSA2ODcuMDQgNDI2LjY2IDY1OS44MiA0NTMuODcgNzYxLjM5IDUxMiA3MDMuMjYgNTcwLjEzIDc2MS4zOSA1OTcuMzQgNjU5LjgyIi8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjI0Ni4yMyA0NTIuMSAyMTcuMzkgNDgwLjk0IDI0OC43NCA1MTIuMjkgMjE3LjM5IDU0My42NCAyNDYuMjMgNTcyLjQ4IDMwNi40MiA1MTIuMjkgMjQ2LjIzIDQ1Mi4xIi8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9Ijc3Ny43NyA0NTEuNTIgODA2LjYxIDQ4MC4zNiA3NzUuMjYgNTExLjcxIDgwNi42MSA1NDMuMDYgNzc3Ljc3IDU3MS45IDcxNy41OCA1MTEuNzEgNzc3Ljc3IDQ1MS41MiIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMyIgcG9pbnRzPSI0MzEuNDkgNzcyLjQgMzkyLjA5IDc4Mi45NiAzODAuNjIgNzQwLjE0IDMzNy44IDc1MS42MSAzMjcuMjQgNzEyLjIyIDQwOS40NiA2OTAuMTkgNDMxLjQ5IDc3Mi40Ii8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjY5Ny4yNiA3MTEuOTMgNjg2LjcxIDc1MS4zMiA2NDMuODggNzM5Ljg1IDYzMi40MSA3ODIuNjcgNTkzLjAxIDc3Mi4xMSA2MTUuMDQgNjg5LjkgNjk3LjI2IDcxMS45MyIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMyIgcG9pbnRzPSI1OTIuNTEgMjUxLjYgNjMxLjkxIDI0MS4wNCA2NDMuMzggMjgzLjg2IDY4Ni4yIDI3Mi4zOSA2OTYuNzYgMzExLjc4IDYxNC41NCAzMzMuODEgNTkyLjUxIDI1MS42Ii8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjMyNi43NCAzMTIuMDcgMzM3LjI5IDI3Mi42OCAzODAuMTIgMjg0LjE1IDM5MS41OSAyNDEuMzMgNDMwLjk5IDI1MS44OSA0MDguOTYgMzM0LjEgMzI2Ljc0IDMxMi4wNyIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtNCIgcG9pbnRzPSIyNjQuMjggMTk2LjA1IDE5MCAyMTUuOTUgMjEwLjgzIDI5My43MiA4Ny44MiAyMjIuNyA0OS4zNyAyODkuMyAxNzIuMzggMzYwLjMyIDk0LjYxIDM4MS4xNiAxMTQuNTIgNDU1LjQ1IDMxOS4xIDQwMC42MyAyNjQuMjggMTk2LjA1Ii8+PHBvbHlnb24gY2xhc3M9ImNscy00IiBwb2ludHM9IjExNC41MiA1NjguNTYgOTQuNjEgNjQyLjg0IDE3Mi4zOCA2NjMuNjggNDkuMzcgNzM0LjcgODcuODIgODAxLjMgMjEwLjgzIDczMC4yOCAxOTAgODA4LjA1IDI2NC4yOCA4MjcuOTUgMzE5LjEgNjIzLjM3IDExNC41MiA1NjguNTYiLz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iMzYyLjI0IDg4NC41MSA0MTYuNjIgOTM4Ljg5IDQ3My41NSA4ODEuOTYgNDczLjU1IDEwMjQgNTUwLjQ1IDEwMjQgNTUwLjQ1IDg4MS45NiA2MDcuMzggOTM4Ljg5IDY2MS43NiA4ODQuNTEgNTEyIDczNC43NCAzNjIuMjQgODg0LjUxIi8+PHBvbHlnb24gY2xhc3M9ImNscy00IiBwb2ludHM9Ijc1OS43MiA4MjcuOTUgODM0IDgwOC4wNSA4MTMuMTcgNzMwLjI4IDkzNi4xOCA4MDEuMyA5NzQuNjMgNzM0LjcgODUxLjYyIDY2My42OCA5MjkuMzkgNjQyLjg0IDkwOS40OCA1NjguNTUgNzA0LjkgNjIzLjM3IDc1OS43MiA4MjcuOTUiLz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iOTA5LjQ4IDQ1NS40NCA5MjkuMzkgMzgxLjE2IDg1MS42MiAzNjAuMzIgOTc0LjYzIDI4OS4zIDkzNi4xOCAyMjIuNyA4MTMuMTcgMjkzLjcyIDgzNCAyMTUuOTUgNzU5LjcyIDE5Ni4wNSA3MDQuOSA0MDAuNjMgOTA5LjQ4IDQ1NS40NCIvPjxwYXRoIGNsYXNzPSJjbHMtMSIgZD0iTTUxMi41NCw1NzkuNDdjLTM3LjQ3LDAtNjcuOTYtMzAuNDktNjcuOTYtNjcuOTZzMzAuNDktNjcuOTYsNjcuOTYtNjcuOTZjMjUuMTEsMCw0Ny4wNiwxMy42OSw1OC44MiwzNGw2OS4xNy0zOS43Ni0xMjguNTMtNzQuMjEtMTI4LjUzLDc0LjIxdjE0OC40MmwxMjguNTMsNzQuMjEsMTI4LjUzLTc0LjIxLTY5LjE3LTQwLjczYy0xMS43NywyMC4zLTMzLjcyLDMzLjk5LTU4LjgyLDMzLjk5WiIvPjwvc3ZnPgo= - description: Configure your Java applications on OpenShift to be profiled and monitored using the Red Hat build of Cryostat. + description: Configure your JMX-based Java applications on OpenShift to be profiled and monitored using the Red Hat build of Cryostat. durationMinutes: 10 - displayName: Configure Java applications with the Red Hat build of Cryostat + displayName: Configure JMX-based Java applications with the Red Hat build of Cryostat introduction: >- Red Hat build of Cryostat is a container-native Java application based on JDK Flight Recorder (JFR). You can use it to monitor the performance of the Java Virtual Machine (JVM) for containerized workloads that run on an OpenShift cluster. - To enable Cryostat to gather, store, and analyze Java Flight Recorder (JFR) data about target applications that run on Java Virtual Machine (JVM)s, you must configure the applications so that Cryostat can detect and connect to them. - - You can use Red Hat build of Cryostat Operator to automatically configure your target application to use the Cryostat Agent to register with a specific Cryostat instance and provide HTTP-based connectivity. + - You can use Red Hat build of Cryostat Operator to automatically configure your target application to use the Cryostat Agent to register with a specific Cryostat instance and provide HTTP-based connectivity by following the **Auto-configure Java applications with the Red Hat build of Cryostat** quick start. - - Alternatively, you can configure your Java applications to allow Java Management Extensions (JMX) connections and use an OpenShift Service for detection and JMX for connectivity. JMX is a standard feature on a JVM with which you can monitor and manage target applications that run on the JVM. You may enable and configure JMX when you start the target application JVM so that Red Hat build of Cryostat can communicate with your JVM over the network using built-in JDK functionality. + - Alternatively, you can configure your Java applications to allow Java Management Extensions (JMX) connections and use an OpenShift Service for detection and JMX for connectivity. JMX is a standard feature on a JVM with which you can monitor and manage target applications that run on the JVM. You may enable and configure JMX when you start the target application JVM so that Red Hat build of Cryostat can communicate with your JVM over the network using built-in JDK functionality. This quick start will explain this JMX-based setup. - If you have not yet installed the Red Hat Build of Cryostat Operator, start with the **Get started with the Red Hat build of Cryostat** quick start. diff --git a/config/openshift/kustomization.yaml b/config/openshift/kustomization.yaml index 5dd1f5dd2..81fd73d90 100644 --- a/config/openshift/kustomization.yaml +++ b/config/openshift/kustomization.yaml @@ -2,7 +2,7 @@ apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization resources: -- cryostat-quickstart.yaml +- cryostat-quickstart-jmx.yaml - console-plugin/clusterrolebinding-cryostat-plugin-patcher.yaml - console-plugin/clusterrolebinding-cryostat-plugin.yaml - console-plugin/clusterrole-cryostat-plugin-patcher.yaml From d18ad23c400b84d444be1ecd550f1b13ad881969 Mon Sep 17 00:00:00 2001 From: Andrew Azores Date: Fri, 7 Feb 2025 16:08:21 -0500 Subject: [PATCH 05/11] add agent autoconfig quickstart --- .../cryostat-quickstart-autoconfig.yaml | 93 +++++++++++++++++++ config/openshift/kustomization.yaml | 1 + 2 files changed, 94 insertions(+) create mode 100644 config/openshift/cryostat-quickstart-autoconfig.yaml diff --git a/config/openshift/cryostat-quickstart-autoconfig.yaml b/config/openshift/cryostat-quickstart-autoconfig.yaml new file mode 100644 index 000000000..6fbbeb26b --- /dev/null +++ b/config/openshift/cryostat-quickstart-autoconfig.yaml @@ -0,0 +1,93 @@ +apiVersion: console.openshift.io/v1 +kind: ConsoleQuickStart +metadata: + annotations: + capability.openshift.io/name: Console + name: configuring-cryostat-autoconfig +spec: + icon: >- + data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz48c3ZnIGlkPSJMYXllcl8xIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAxMDI0IDEwMjQiPjxkZWZzPjxzdHlsZT4uY2xzLTF7ZmlsbDojZmZmO30uY2xzLTJ7ZmlsbDojMWI0OTY1O30uY2xzLTN7ZmlsbDojOTVjOWU5O30uY2xzLTR7ZmlsbDojNWZhOGQzO308L3N0eWxlPjwvZGVmcz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iNjYxLjc2IDEzOS40OSA2MDcuMzggODUuMTEgNTUwLjQ1IDE0Mi4wNCA1NTAuNDUgMCA0NzMuNTUgMCA0NzMuNTUgMTQyLjA0IDQxNi42MiA4NS4xMSAzNjIuMjQgMTM5LjQ5IDUxMiAyODkuMjYgNjYxLjc2IDEzOS40OSIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMiIgcG9pbnRzPSI1OTcuMzQgNjU5LjgyIDY5OC45MiA2ODcuMDQgNjc3LjY0IDYwNy42MyA3NTcuMDQgNTg2LjM1IDY4Mi42OSA1MTIgNzU3LjA0IDQzNy42NSA2NzcuNjQgNDE2LjM3IDY5OC45MSAzMzYuOTYgNTk3LjM0IDM2NC4xOCA1NzAuMTMgMjYyLjYxIDUxMiAzMjAuNzQgNDUzLjg3IDI2Mi42MSA0MjYuNjYgMzY0LjE4IDMyNS4wOSAzMzYuOTYgMzQ2LjM2IDQxNi4zNyAyNjYuOTYgNDM3LjY1IDM0MS4zMSA1MTIgMjY2Ljk2IDU4Ni4zNSAzNDYuMzYgNjA3LjYzIDMyNS4wOSA2ODcuMDQgNDI2LjY2IDY1OS44MiA0NTMuODcgNzYxLjM5IDUxMiA3MDMuMjYgNTcwLjEzIDc2MS4zOSA1OTcuMzQgNjU5LjgyIi8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjI0Ni4yMyA0NTIuMSAyMTcuMzkgNDgwLjk0IDI0OC43NCA1MTIuMjkgMjE3LjM5IDU0My42NCAyNDYuMjMgNTcyLjQ4IDMwNi40MiA1MTIuMjkgMjQ2LjIzIDQ1Mi4xIi8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9Ijc3Ny43NyA0NTEuNTIgODA2LjYxIDQ4MC4zNiA3NzUuMjYgNTExLjcxIDgwNi42MSA1NDMuMDYgNzc3Ljc3IDU3MS45IDcxNy41OCA1MTEuNzEgNzc3Ljc3IDQ1MS41MiIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMyIgcG9pbnRzPSI0MzEuNDkgNzcyLjQgMzkyLjA5IDc4Mi45NiAzODAuNjIgNzQwLjE0IDMzNy44IDc1MS42MSAzMjcuMjQgNzEyLjIyIDQwOS40NiA2OTAuMTkgNDMxLjQ5IDc3Mi40Ii8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjY5Ny4yNiA3MTEuOTMgNjg2LjcxIDc1MS4zMiA2NDMuODggNzM5Ljg1IDYzMi40MSA3ODIuNjcgNTkzLjAxIDc3Mi4xMSA2MTUuMDQgNjg5LjkgNjk3LjI2IDcxMS45MyIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMyIgcG9pbnRzPSI1OTIuNTEgMjUxLjYgNjMxLjkxIDI0MS4wNCA2NDMuMzggMjgzLjg2IDY4Ni4yIDI3Mi4zOSA2OTYuNzYgMzExLjc4IDYxNC41NCAzMzMuODEgNTkyLjUxIDI1MS42Ii8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjMyNi43NCAzMTIuMDcgMzM3LjI5IDI3Mi42OCAzODAuMTIgMjg0LjE1IDM5MS41OSAyNDEuMzMgNDMwLjk5IDI1MS44OSA0MDguOTYgMzM0LjEgMzI2Ljc0IDMxMi4wNyIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtNCIgcG9pbnRzPSIyNjQuMjggMTk2LjA1IDE5MCAyMTUuOTUgMjEwLjgzIDI5My43MiA4Ny44MiAyMjIuNyA0OS4zNyAyODkuMyAxNzIuMzggMzYwLjMyIDk0LjYxIDM4MS4xNiAxMTQuNTIgNDU1LjQ1IDMxOS4xIDQwMC42MyAyNjQuMjggMTk2LjA1Ii8+PHBvbHlnb24gY2xhc3M9ImNscy00IiBwb2ludHM9IjExNC41MiA1NjguNTYgOTQuNjEgNjQyLjg0IDE3Mi4zOCA2NjMuNjggNDkuMzcgNzM0LjcgODcuODIgODAxLjMgMjEwLjgzIDczMC4yOCAxOTAgODA4LjA1IDI2NC4yOCA4MjcuOTUgMzE5LjEgNjIzLjM3IDExNC41MiA1NjguNTYiLz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iMzYyLjI0IDg4NC41MSA0MTYuNjIgOTM4Ljg5IDQ3My41NSA4ODEuOTYgNDczLjU1IDEwMjQgNTUwLjQ1IDEwMjQgNTUwLjQ1IDg4MS45NiA2MDcuMzggOTM4Ljg5IDY2MS43NiA4ODQuNTEgNTEyIDczNC43NCAzNjIuMjQgODg0LjUxIi8+PHBvbHlnb24gY2xhc3M9ImNscy00IiBwb2ludHM9Ijc1OS43MiA4MjcuOTUgODM0IDgwOC4wNSA4MTMuMTcgNzMwLjI4IDkzNi4xOCA4MDEuMyA5NzQuNjMgNzM0LjcgODUxLjYyIDY2My42OCA5MjkuMzkgNjQyLjg0IDkwOS40OCA1NjguNTUgNzA0LjkgNjIzLjM3IDc1OS43MiA4MjcuOTUiLz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iOTA5LjQ4IDQ1NS40NCA5MjkuMzkgMzgxLjE2IDg1MS42MiAzNjAuMzIgOTc0LjYzIDI4OS4zIDkzNi4xOCAyMjIuNyA4MTMuMTcgMjkzLjcyIDgzNCAyMTUuOTUgNzU5LjcyIDE5Ni4wNSA3MDQuOSA0MDAuNjMgOTA5LjQ4IDQ1NS40NCIvPjxwYXRoIGNsYXNzPSJjbHMtMSIgZD0iTTUxMi41NCw1NzkuNDdjLTM3LjQ3LDAtNjcuOTYtMzAuNDktNjcuOTYtNjcuOTZzMzAuNDktNjcuOTYsNjcuOTYtNjcuOTZjMjUuMTEsMCw0Ny4wNiwxMy42OSw1OC44MiwzNGw2OS4xNy0zOS43Ni0xMjguNTMtNzQuMjEtMTI4LjUzLDc0LjIxdjE0OC40MmwxMjguNTMsNzQuMjEsMTI4LjUzLTc0LjIxLTY5LjE3LTQwLjczYy0xMS43NywyMC4zLTMzLjcyLDMzLjk5LTU4LjgyLDMzLjk5WiIvPjwvc3ZnPgo= + description: Automatically configure your Java applications on OpenShift to be profiled and monitored using the Red Hat build of Cryostat and Cryostat Agent. + durationMinutes: 10 + displayName: Auto-configure Java applications with the Red Hat build of Cryostat + introduction: >- + Red Hat build of Cryostat is a container-native Java application based on JDK Flight Recorder (JFR). You can use it to monitor the performance of the Java Virtual Machine (JVM) for containerized workloads that run on an OpenShift cluster. + + - To enable Cryostat to gather, store, and analyze Java Flight Recorder (JFR) data about target applications that run on Java Virtual Machine (JVM)s, you must configure the applications so that Cryostat can detect and connect to them. + + - You can use Red Hat build of Cryostat Operator to automatically configure your target application to use the Cryostat Agent to register with a specific Cryostat instance and provide HTTP-based connectivity by following the **Auto-configure Java applications with the Red Hat build of Cryostat** quick start. + + - Alternatively, you can configure your Java applications to allow Java Management Extensions (JMX) connections and use an OpenShift Service for detection and JMX for connectivity. JMX is a standard feature on a JVM with which you can monitor and manage target applications that run on the JVM. You may enable and configure JMX when you start the target application JVM so that Red Hat build of Cryostat can communicate with your JVM over the network using built-in JDK functionality. Follow the **Configure JMX-based Java applications with the Red Hat build of Cryostat** quick start for instructions on that setup. + + - If you have not yet installed the Red Hat Build of Cryostat Operator, start with the **Get started with the Red Hat build of Cryostat** quick start. + + - **Note**: The quickstart uses a sample [Quarkus application](https://github.com/quarkusio/quarkus-quickstarts). You can deploy your own application or follow the **Get started with Quarkus using s2i** quick start. + tasks: + - title: Enable **Cryostat Agent instrumentation** on your Java Application + description: > + To enable Cryostat Agent instrumentation: + + 1. In the main navigation, click the dropdown menu and select **Administrator**. + + 1. In the navigation menu, click **Workloads > Deployments**. + + 1. Click on the quarkus-quickstarts deployment name (or your application's deployment name). + + 1. Click **YAML** + + Alternatively, + + 1. In the main navigation, click the dropdown menu and select **Developer**. + + 1. In the navigation menu, click **Topology**. + + 1. Click on the quarkus-quickstarts deployment (or your application's deployment). + + 1. Click **Actions > Edit Deployment**. + + 1. Click **Configure via: > YAML view**. + + Then, + + 1. In the text editor, add the following labels to the `.spec.template.metadata.labels` section: + - **Name**: `cryostat.io/name` + - **Value**: Set this to the name of your Cryostat Custom Resource instance. + - **Name**: `cryostat.io/namespace` + - **Value**: Set this to the installation namespace of your Cryostat Custom Resource instance. + + 1. Click **Save.** + review: + failedTaskHelp: >- + This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/3/html/getting_started_with_cryostat/configuring_java_applications#working_with_cryostat_agent) + about this topic. + instructions: > + #### Click **Reload** at the bottom of the **YAML** tab. + + Do you see a the expected labels under the `.spec.template.metadata.labels`? + - title: View your Java Application as a target in Cryostat + description: > + View your Java application as a target in the Red Hat build of Cryostat web application: + + 1. In the main navigation, click the dropdown menu and select **Developer**. + + 1. In the navigation menu, click **Topology**. + + 1. The external link icon on **cryostat-sample deployment** represents the route URL. + + 1. Click the external link icon to open the URL and run the Cryostat web application in a new browser tab. + + 1. Enter your Red Hat OpenShift credentials to log in to the Cryostat web application. + + 1. In the web application, click **Recordings** in the navigation menu. + + 1. View quarkus-quickstarts (or your deployed application) in the **Targets** list. + review: + failedTaskHelp: >- + This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications) + about this topic. + instructions: |- + #### Verify your Java application is running on Red Hat build of Cryostat web application: + + Did the Cryostat web application open in a separate browser window? + conclusion: >- + Your Java application has now been configured to be detected by Cryostat. To profile your Java applications with Cryostat, please follow [this documentation](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/using_cryostat_to_manage_a_jfr_recording/index). diff --git a/config/openshift/kustomization.yaml b/config/openshift/kustomization.yaml index 81fd73d90..3a80a1cad 100644 --- a/config/openshift/kustomization.yaml +++ b/config/openshift/kustomization.yaml @@ -3,6 +3,7 @@ kind: Kustomization resources: - cryostat-quickstart-jmx.yaml +- cryostat-quickstart-autoconfig.yaml - console-plugin/clusterrolebinding-cryostat-plugin-patcher.yaml - console-plugin/clusterrolebinding-cryostat-plugin.yaml - console-plugin/clusterrole-cryostat-plugin-patcher.yaml From 55e611ae8117e5e2c6aea7775f5f401fed5b3120 Mon Sep 17 00:00:00 2001 From: Andrew Azores Date: Sat, 8 Feb 2025 10:21:56 -0500 Subject: [PATCH 06/11] bundle --- ...ole.openshift.io_v1_consolequickstart.yaml | 67 +++++++++++++ ...ole.openshift.io_v1_consolequickstart.yaml | 94 +++++++++++++++++++ ...yostat-operator.clusterserviceversion.yaml | 2 +- 3 files changed, 162 insertions(+), 1 deletion(-) create mode 100644 bundle/manifests/configuring-cryostat-autoconfig_console.openshift.io_v1_consolequickstart.yaml create mode 100644 bundle/manifests/configuring-cryostat-jmx_console.openshift.io_v1_consolequickstart.yaml diff --git a/bundle/manifests/configuring-cryostat-autoconfig_console.openshift.io_v1_consolequickstart.yaml b/bundle/manifests/configuring-cryostat-autoconfig_console.openshift.io_v1_consolequickstart.yaml new file mode 100644 index 000000000..3116ecc41 --- /dev/null +++ b/bundle/manifests/configuring-cryostat-autoconfig_console.openshift.io_v1_consolequickstart.yaml @@ -0,0 +1,67 @@ +apiVersion: console.openshift.io/v1 +kind: ConsoleQuickStart +metadata: + annotations: + capability.openshift.io/name: Console + name: configuring-cryostat-autoconfig +spec: + conclusion: Your Java application has now been configured to be detected by Cryostat. + To profile your Java applications with Cryostat, please follow [this documentation](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/using_cryostat_to_manage_a_jfr_recording/index). + description: Automatically configure your Java applications on OpenShift to be profiled + and monitored using the Red Hat build of Cryostat and Cryostat Agent. + displayName: Auto-configure Java applications with the Red Hat build of Cryostat + durationMinutes: 10 + icon: data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz48c3ZnIGlkPSJMYXllcl8xIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAxMDI0IDEwMjQiPjxkZWZzPjxzdHlsZT4uY2xzLTF7ZmlsbDojZmZmO30uY2xzLTJ7ZmlsbDojMWI0OTY1O30uY2xzLTN7ZmlsbDojOTVjOWU5O30uY2xzLTR7ZmlsbDojNWZhOGQzO308L3N0eWxlPjwvZGVmcz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iNjYxLjc2IDEzOS40OSA2MDcuMzggODUuMTEgNTUwLjQ1IDE0Mi4wNCA1NTAuNDUgMCA0NzMuNTUgMCA0NzMuNTUgMTQyLjA0IDQxNi42MiA4NS4xMSAzNjIuMjQgMTM5LjQ5IDUxMiAyODkuMjYgNjYxLjc2IDEzOS40OSIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMiIgcG9pbnRzPSI1OTcuMzQgNjU5LjgyIDY5OC45MiA2ODcuMDQgNjc3LjY0IDYwNy42MyA3NTcuMDQgNTg2LjM1IDY4Mi42OSA1MTIgNzU3LjA0IDQzNy42NSA2NzcuNjQgNDE2LjM3IDY5OC45MSAzMzYuOTYgNTk3LjM0IDM2NC4xOCA1NzAuMTMgMjYyLjYxIDUxMiAzMjAuNzQgNDUzLjg3IDI2Mi42MSA0MjYuNjYgMzY0LjE4IDMyNS4wOSAzMzYuOTYgMzQ2LjM2IDQxNi4zNyAyNjYuOTYgNDM3LjY1IDM0MS4zMSA1MTIgMjY2Ljk2IDU4Ni4zNSAzNDYuMzYgNjA3LjYzIDMyNS4wOSA2ODcuMDQgNDI2LjY2IDY1OS44MiA0NTMuODcgNzYxLjM5IDUxMiA3MDMuMjYgNTcwLjEzIDc2MS4zOSA1OTcuMzQgNjU5LjgyIi8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjI0Ni4yMyA0NTIuMSAyMTcuMzkgNDgwLjk0IDI0OC43NCA1MTIuMjkgMjE3LjM5IDU0My42NCAyNDYuMjMgNTcyLjQ4IDMwNi40MiA1MTIuMjkgMjQ2LjIzIDQ1Mi4xIi8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9Ijc3Ny43NyA0NTEuNTIgODA2LjYxIDQ4MC4zNiA3NzUuMjYgNTExLjcxIDgwNi42MSA1NDMuMDYgNzc3Ljc3IDU3MS45IDcxNy41OCA1MTEuNzEgNzc3Ljc3IDQ1MS41MiIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMyIgcG9pbnRzPSI0MzEuNDkgNzcyLjQgMzkyLjA5IDc4Mi45NiAzODAuNjIgNzQwLjE0IDMzNy44IDc1MS42MSAzMjcuMjQgNzEyLjIyIDQwOS40NiA2OTAuMTkgNDMxLjQ5IDc3Mi40Ii8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjY5Ny4yNiA3MTEuOTMgNjg2LjcxIDc1MS4zMiA2NDMuODggNzM5Ljg1IDYzMi40MSA3ODIuNjcgNTkzLjAxIDc3Mi4xMSA2MTUuMDQgNjg5LjkgNjk3LjI2IDcxMS45MyIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMyIgcG9pbnRzPSI1OTIuNTEgMjUxLjYgNjMxLjkxIDI0MS4wNCA2NDMuMzggMjgzLjg2IDY4Ni4yIDI3Mi4zOSA2OTYuNzYgMzExLjc4IDYxNC41NCAzMzMuODEgNTkyLjUxIDI1MS42Ii8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjMyNi43NCAzMTIuMDcgMzM3LjI5IDI3Mi42OCAzODAuMTIgMjg0LjE1IDM5MS41OSAyNDEuMzMgNDMwLjk5IDI1MS44OSA0MDguOTYgMzM0LjEgMzI2Ljc0IDMxMi4wNyIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtNCIgcG9pbnRzPSIyNjQuMjggMTk2LjA1IDE5MCAyMTUuOTUgMjEwLjgzIDI5My43MiA4Ny44MiAyMjIuNyA0OS4zNyAyODkuMyAxNzIuMzggMzYwLjMyIDk0LjYxIDM4MS4xNiAxMTQuNTIgNDU1LjQ1IDMxOS4xIDQwMC42MyAyNjQuMjggMTk2LjA1Ii8+PHBvbHlnb24gY2xhc3M9ImNscy00IiBwb2ludHM9IjExNC41MiA1NjguNTYgOTQuNjEgNjQyLjg0IDE3Mi4zOCA2NjMuNjggNDkuMzcgNzM0LjcgODcuODIgODAxLjMgMjEwLjgzIDczMC4yOCAxOTAgODA4LjA1IDI2NC4yOCA4MjcuOTUgMzE5LjEgNjIzLjM3IDExNC41MiA1NjguNTYiLz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iMzYyLjI0IDg4NC41MSA0MTYuNjIgOTM4Ljg5IDQ3My41NSA4ODEuOTYgNDczLjU1IDEwMjQgNTUwLjQ1IDEwMjQgNTUwLjQ1IDg4MS45NiA2MDcuMzggOTM4Ljg5IDY2MS43NiA4ODQuNTEgNTEyIDczNC43NCAzNjIuMjQgODg0LjUxIi8+PHBvbHlnb24gY2xhc3M9ImNscy00IiBwb2ludHM9Ijc1OS43MiA4MjcuOTUgODM0IDgwOC4wNSA4MTMuMTcgNzMwLjI4IDkzNi4xOCA4MDEuMyA5NzQuNjMgNzM0LjcgODUxLjYyIDY2My42OCA5MjkuMzkgNjQyLjg0IDkwOS40OCA1NjguNTUgNzA0LjkgNjIzLjM3IDc1OS43MiA4MjcuOTUiLz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iOTA5LjQ4IDQ1NS40NCA5MjkuMzkgMzgxLjE2IDg1MS42MiAzNjAuMzIgOTc0LjYzIDI4OS4zIDkzNi4xOCAyMjIuNyA4MTMuMTcgMjkzLjcyIDgzNCAyMTUuOTUgNzU5LjcyIDE5Ni4wNSA3MDQuOSA0MDAuNjMgOTA5LjQ4IDQ1NS40NCIvPjxwYXRoIGNsYXNzPSJjbHMtMSIgZD0iTTUxMi41NCw1NzkuNDdjLTM3LjQ3LDAtNjcuOTYtMzAuNDktNjcuOTYtNjcuOTZzMzAuNDktNjcuOTYsNjcuOTYtNjcuOTZjMjUuMTEsMCw0Ny4wNiwxMy42OSw1OC44MiwzNGw2OS4xNy0zOS43Ni0xMjguNTMtNzQuMjEtMTI4LjUzLDc0LjIxdjE0OC40MmwxMjguNTMsNzQuMjEsMTI4LjUzLTc0LjIxLTY5LjE3LTQwLjczYy0xMS43NywyMC4zLTMzLjcyLDMzLjk5LTU4LjgyLDMzLjk5WiIvPjwvc3ZnPgo= + introduction: |- + Red Hat build of Cryostat is a container-native Java application based on JDK Flight Recorder (JFR). You can use it to monitor the performance of the Java Virtual Machine (JVM) for containerized workloads that run on an OpenShift cluster. + - To enable Cryostat to gather, store, and analyze Java Flight Recorder (JFR) data about target applications that run on Java Virtual Machine (JVM)s, you must configure the applications so that Cryostat can detect and connect to them. + - You can use Red Hat build of Cryostat Operator to automatically configure your target application to use the Cryostat Agent to register with a specific Cryostat instance and provide HTTP-based connectivity by following the **Auto-configure Java applications with the Red Hat build of Cryostat** quick start. + - Alternatively, you can configure your Java applications to allow Java Management Extensions (JMX) connections and use an OpenShift Service for detection and JMX for connectivity. JMX is a standard feature on a JVM with which you can monitor and manage target applications that run on the JVM. You may enable and configure JMX when you start the target application JVM so that Red Hat build of Cryostat can communicate with your JVM over the network using built-in JDK functionality. Follow the **Configure JMX-based Java applications with the Red Hat build of Cryostat** quick start for instructions on that setup. + - If you have not yet installed the Red Hat Build of Cryostat Operator, start with the **Get started with the Red Hat build of Cryostat** quick start. + - **Note**: The quickstart uses a sample [Quarkus application](https://github.com/quarkusio/quarkus-quickstarts). You can deploy your own application or follow the **Get started with Quarkus using s2i** quick start. + tasks: + - description: | + To enable Cryostat Agent instrumentation: + 1. In the main navigation, click the dropdown menu and select **Administrator**. + 1. In the navigation menu, click **Workloads > Deployments**. + 1. Click on the quarkus-quickstarts deployment name (or your application's deployment name). + 1. Click **YAML** + Alternatively, + 1. In the main navigation, click the dropdown menu and select **Developer**. + 1. In the navigation menu, click **Topology**. + 1. Click on the quarkus-quickstarts deployment (or your application's deployment). + 1. Click **Actions > Edit Deployment**. + 1. Click **Configure via: > YAML view**. + Then, + 1. In the text editor, add the following labels to the `.spec.template.metadata.labels` section: + + - **Name**: `cryostat.io/name` + - **Value**: Set this to the name of your Cryostat Custom Resource instance. + - **Name**: `cryostat.io/namespace` + - **Value**: Set this to the installation namespace of your Cryostat Custom Resource instance. + + 1. Click **Save.** + review: + failedTaskHelp: This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/3/html/getting_started_with_cryostat/configuring_java_applications#working_with_cryostat_agent) + about this topic. + instructions: | + #### Click **Reload** at the bottom of the **YAML** tab. + Do you see a the expected labels under the `.spec.template.metadata.labels`? + title: Enable **Cryostat Agent instrumentation** on your Java Application + - description: | + View your Java application as a target in the Red Hat build of Cryostat web application: + 1. In the main navigation, click the dropdown menu and select **Developer**. + 1. In the navigation menu, click **Topology**. + 1. The external link icon on **cryostat-sample deployment** represents the route URL. + 1. Click the external link icon to open the URL and run the Cryostat web application in a new browser tab. + 1. Enter your Red Hat OpenShift credentials to log in to the Cryostat web application. + 1. In the web application, click **Recordings** in the navigation menu. + 1. View quarkus-quickstarts (or your deployed application) in the **Targets** list. + review: + failedTaskHelp: This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications) + about this topic. + instructions: |- + #### Verify your Java application is running on Red Hat build of Cryostat web application: + + Did the Cryostat web application open in a separate browser window? + title: View your Java Application as a target in Cryostat diff --git a/bundle/manifests/configuring-cryostat-jmx_console.openshift.io_v1_consolequickstart.yaml b/bundle/manifests/configuring-cryostat-jmx_console.openshift.io_v1_consolequickstart.yaml new file mode 100644 index 000000000..fbfcda680 --- /dev/null +++ b/bundle/manifests/configuring-cryostat-jmx_console.openshift.io_v1_consolequickstart.yaml @@ -0,0 +1,94 @@ +apiVersion: console.openshift.io/v1 +kind: ConsoleQuickStart +metadata: + annotations: + capability.openshift.io/name: Console + name: configuring-cryostat-jmx +spec: + conclusion: Your Java application has now been configured to be detected by Cryostat. + To profile your Java applications with Cryostat, please follow [this documentation](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/using_cryostat_to_manage_a_jfr_recording/index). + description: Configure your JMX-based Java applications on OpenShift to be profiled + and monitored using the Red Hat build of Cryostat. + displayName: Configure JMX-based Java applications with the Red Hat build of Cryostat + durationMinutes: 10 + icon: data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz48c3ZnIGlkPSJMYXllcl8xIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAxMDI0IDEwMjQiPjxkZWZzPjxzdHlsZT4uY2xzLTF7ZmlsbDojZmZmO30uY2xzLTJ7ZmlsbDojMWI0OTY1O30uY2xzLTN7ZmlsbDojOTVjOWU5O30uY2xzLTR7ZmlsbDojNWZhOGQzO308L3N0eWxlPjwvZGVmcz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iNjYxLjc2IDEzOS40OSA2MDcuMzggODUuMTEgNTUwLjQ1IDE0Mi4wNCA1NTAuNDUgMCA0NzMuNTUgMCA0NzMuNTUgMTQyLjA0IDQxNi42MiA4NS4xMSAzNjIuMjQgMTM5LjQ5IDUxMiAyODkuMjYgNjYxLjc2IDEzOS40OSIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMiIgcG9pbnRzPSI1OTcuMzQgNjU5LjgyIDY5OC45MiA2ODcuMDQgNjc3LjY0IDYwNy42MyA3NTcuMDQgNTg2LjM1IDY4Mi42OSA1MTIgNzU3LjA0IDQzNy42NSA2NzcuNjQgNDE2LjM3IDY5OC45MSAzMzYuOTYgNTk3LjM0IDM2NC4xOCA1NzAuMTMgMjYyLjYxIDUxMiAzMjAuNzQgNDUzLjg3IDI2Mi42MSA0MjYuNjYgMzY0LjE4IDMyNS4wOSAzMzYuOTYgMzQ2LjM2IDQxNi4zNyAyNjYuOTYgNDM3LjY1IDM0MS4zMSA1MTIgMjY2Ljk2IDU4Ni4zNSAzNDYuMzYgNjA3LjYzIDMyNS4wOSA2ODcuMDQgNDI2LjY2IDY1OS44MiA0NTMuODcgNzYxLjM5IDUxMiA3MDMuMjYgNTcwLjEzIDc2MS4zOSA1OTcuMzQgNjU5LjgyIi8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjI0Ni4yMyA0NTIuMSAyMTcuMzkgNDgwLjk0IDI0OC43NCA1MTIuMjkgMjE3LjM5IDU0My42NCAyNDYuMjMgNTcyLjQ4IDMwNi40MiA1MTIuMjkgMjQ2LjIzIDQ1Mi4xIi8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9Ijc3Ny43NyA0NTEuNTIgODA2LjYxIDQ4MC4zNiA3NzUuMjYgNTExLjcxIDgwNi42MSA1NDMuMDYgNzc3Ljc3IDU3MS45IDcxNy41OCA1MTEuNzEgNzc3Ljc3IDQ1MS41MiIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMyIgcG9pbnRzPSI0MzEuNDkgNzcyLjQgMzkyLjA5IDc4Mi45NiAzODAuNjIgNzQwLjE0IDMzNy44IDc1MS42MSAzMjcuMjQgNzEyLjIyIDQwOS40NiA2OTAuMTkgNDMxLjQ5IDc3Mi40Ii8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjY5Ny4yNiA3MTEuOTMgNjg2LjcxIDc1MS4zMiA2NDMuODggNzM5Ljg1IDYzMi40MSA3ODIuNjcgNTkzLjAxIDc3Mi4xMSA2MTUuMDQgNjg5LjkgNjk3LjI2IDcxMS45MyIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMyIgcG9pbnRzPSI1OTIuNTEgMjUxLjYgNjMxLjkxIDI0MS4wNCA2NDMuMzggMjgzLjg2IDY4Ni4yIDI3Mi4zOSA2OTYuNzYgMzExLjc4IDYxNC41NCAzMzMuODEgNTkyLjUxIDI1MS42Ii8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjMyNi43NCAzMTIuMDcgMzM3LjI5IDI3Mi42OCAzODAuMTIgMjg0LjE1IDM5MS41OSAyNDEuMzMgNDMwLjk5IDI1MS44OSA0MDguOTYgMzM0LjEgMzI2Ljc0IDMxMi4wNyIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtNCIgcG9pbnRzPSIyNjQuMjggMTk2LjA1IDE5MCAyMTUuOTUgMjEwLjgzIDI5My43MiA4Ny44MiAyMjIuNyA0OS4zNyAyODkuMyAxNzIuMzggMzYwLjMyIDk0LjYxIDM4MS4xNiAxMTQuNTIgNDU1LjQ1IDMxOS4xIDQwMC42MyAyNjQuMjggMTk2LjA1Ii8+PHBvbHlnb24gY2xhc3M9ImNscy00IiBwb2ludHM9IjExNC41MiA1NjguNTYgOTQuNjEgNjQyLjg0IDE3Mi4zOCA2NjMuNjggNDkuMzcgNzM0LjcgODcuODIgODAxLjMgMjEwLjgzIDczMC4yOCAxOTAgODA4LjA1IDI2NC4yOCA4MjcuOTUgMzE5LjEgNjIzLjM3IDExNC41MiA1NjguNTYiLz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iMzYyLjI0IDg4NC41MSA0MTYuNjIgOTM4Ljg5IDQ3My41NSA4ODEuOTYgNDczLjU1IDEwMjQgNTUwLjQ1IDEwMjQgNTUwLjQ1IDg4MS45NiA2MDcuMzggOTM4Ljg5IDY2MS43NiA4ODQuNTEgNTEyIDczNC43NCAzNjIuMjQgODg0LjUxIi8+PHBvbHlnb24gY2xhc3M9ImNscy00IiBwb2ludHM9Ijc1OS43MiA4MjcuOTUgODM0IDgwOC4wNSA4MTMuMTcgNzMwLjI4IDkzNi4xOCA4MDEuMyA5NzQuNjMgNzM0LjcgODUxLjYyIDY2My42OCA5MjkuMzkgNjQyLjg0IDkwOS40OCA1NjguNTUgNzA0LjkgNjIzLjM3IDc1OS43MiA4MjcuOTUiLz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iOTA5LjQ4IDQ1NS40NCA5MjkuMzkgMzgxLjE2IDg1MS42MiAzNjAuMzIgOTc0LjYzIDI4OS4zIDkzNi4xOCAyMjIuNyA4MTMuMTcgMjkzLjcyIDgzNCAyMTUuOTUgNzU5LjcyIDE5Ni4wNSA3MDQuOSA0MDAuNjMgOTA5LjQ4IDQ1NS40NCIvPjxwYXRoIGNsYXNzPSJjbHMtMSIgZD0iTTUxMi41NCw1NzkuNDdjLTM3LjQ3LDAtNjcuOTYtMzAuNDktNjcuOTYtNjcuOTZzMzAuNDktNjcuOTYsNjcuOTYtNjcuOTZjMjUuMTEsMCw0Ny4wNiwxMy42OSw1OC44MiwzNGw2OS4xNy0zOS43Ni0xMjguNTMtNzQuMjEtMTI4LjUzLDc0LjIxdjE0OC40MmwxMjguNTMsNzQuMjEsMTI4LjUzLTc0LjIxLTY5LjE3LTQwLjczYy0xMS43NywyMC4zLTMzLjcyLDMzLjk5LTU4LjgyLDMzLjk5WiIvPjwvc3ZnPgo= + introduction: |- + Red Hat build of Cryostat is a container-native Java application based on JDK Flight Recorder (JFR). You can use it to monitor the performance of the Java Virtual Machine (JVM) for containerized workloads that run on an OpenShift cluster. + - To enable Cryostat to gather, store, and analyze Java Flight Recorder (JFR) data about target applications that run on Java Virtual Machine (JVM)s, you must configure the applications so that Cryostat can detect and connect to them. + - You can use Red Hat build of Cryostat Operator to automatically configure your target application to use the Cryostat Agent to register with a specific Cryostat instance and provide HTTP-based connectivity by following the **Auto-configure Java applications with the Red Hat build of Cryostat** quick start. + - Alternatively, you can configure your Java applications to allow Java Management Extensions (JMX) connections and use an OpenShift Service for detection and JMX for connectivity. JMX is a standard feature on a JVM with which you can monitor and manage target applications that run on the JVM. You may enable and configure JMX when you start the target application JVM so that Red Hat build of Cryostat can communicate with your JVM over the network using built-in JDK functionality. This quick start will explain this JMX-based setup. + - If you have not yet installed the Red Hat Build of Cryostat Operator, start with the **Get started with the Red Hat build of Cryostat** quick start. + - **Note**: The quickstart uses a sample [Quarkus application](https://github.com/quarkusio/quarkus-quickstarts). You can deploy your own application or follow the **Get started with Quarkus using s2i** quick start. + tasks: + - description: | + To enable remote JMX connections: + 1. In the main navigation, click the dropdown menu and select **Administrator**. + 1. In the navigation menu, click **Workloads > Deployments**. + 1. Click on the quarkus-quickstarts deployment name (or your application's deployment name). + 1. Click **Environment.** + 1. In the **Single values (env)** section, add the following environment variable: + + - **Name**: `JAVA_OPTS_APPEND` + - **Value**: + ``` + -Dcom.sun.management.jmxremote.port=9091 + -Dcom.sun.management.jmxremote.authenticate=false + -Dcom.sun.management.jmxremote.ssl=false + ``` + + Note: This method enables remote JMX without authentication. For details on configuring authentication with SSL/TLS for Remote JMX, see [Configuring Java applications](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications). + + 1. Click **Save.** + review: + failedTaskHelp: This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications) + about this topic. + instructions: | + #### Click **Reload** at the bottom of the **Environment** tab. + Do you see a **single values entry** for **`JAVA_OPTS_APPEND`**? + title: Enable **Remote Java Management Extensions (JMX) connections** on your + Java Application + - description: | + To update Red Hat OpenShift Service with the remote JMX port: + 1. In the main navigation, click the dropdown menu and select **Administrator**. + 1. In the navigation menu, click **Networking > Services**. + 1. Click on the quarkus-quickstarts service name (or your application's service name). + 1. Click the “YAML” tab to open the YAML editor. + 1. In the **spec > ports** section, add a new port for jfr-jmx + + ``` + - name: jfr-jmx + protocol: TCP + port: 9091 + targetPort: 9091 + ``` + + 1. Click **Save**. + review: + failedTaskHelp: This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications) + about this topic. + instructions: | + #### Verify that the service port is added to the sample resource: + 1. In the main navigation, click the dropdown menu and select **Developer**. + 1. In the navigation menu, click **Topology**. + 1. Click on the quarkus-quickstarts deployment name (or your application's service name). + 1. Click on the **Resources** tab. + + Do you see **Service port: jfr-jmx -> Pod port: 9091** in the quarkus-quickstarts service? + title: Updating Red Hat OpenShift Service with the remote JMX port + - description: | + View your Java application as a target in the Red Hat build of Cryostat web application: + 1. In the main navigation, click the dropdown menu and select **Developer**. + 1. In the navigation menu, click **Topology**. + 1. The external link icon on **cryostat-sample deployment** represents the route URL. + 1. Click the external link icon to open the URL and run the Cryostat web application in a new browser tab. + 1. Enter your Red Hat OpenShift credentials to log in to the Cryostat web application. + 1. In the web application, click **Recordings** in the navigation menu. + 1. View quarkus-quickstarts (or your deployed application) in the **Targets** list. + review: + failedTaskHelp: This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications) + about this topic. + instructions: |- + #### Verify your Java application is running on Red Hat build of Cryostat web application: + + Did the Cryostat web application open in a separate browser window? + title: View your Java Application as a target in Cryostat diff --git a/bundle/manifests/cryostat-operator.clusterserviceversion.yaml b/bundle/manifests/cryostat-operator.clusterserviceversion.yaml index 6888dfe49..5cdbd8493 100644 --- a/bundle/manifests/cryostat-operator.clusterserviceversion.yaml +++ b/bundle/manifests/cryostat-operator.clusterserviceversion.yaml @@ -24,7 +24,7 @@ metadata: capabilities: Seamless Upgrades categories: Monitoring, Developer Tools containerImage: quay.io/cryostat/cryostat-operator:4.1.0-dev - createdAt: "2025-02-05T19:21:11Z" + createdAt: "2025-02-08T15:20:55Z" description: JVM monitoring and profiling tool operatorframework.io/initialization-resource: |- { From 982519b553e2b53c8de98c859f5e43ce8793c802 Mon Sep 17 00:00:00 2001 From: Andrew Azores Date: Fri, 14 Feb 2025 15:54:34 -0500 Subject: [PATCH 07/11] link quickstarts to each other --- config/openshift/cryostat-quickstart-autoconfig.yaml | 2 ++ config/openshift/cryostat-quickstart-jmx.yaml | 2 ++ 2 files changed, 4 insertions(+) diff --git a/config/openshift/cryostat-quickstart-autoconfig.yaml b/config/openshift/cryostat-quickstart-autoconfig.yaml index 6fbbeb26b..c54505cbf 100644 --- a/config/openshift/cryostat-quickstart-autoconfig.yaml +++ b/config/openshift/cryostat-quickstart-autoconfig.yaml @@ -10,6 +10,8 @@ spec: description: Automatically configure your Java applications on OpenShift to be profiled and monitored using the Red Hat build of Cryostat and Cryostat Agent. durationMinutes: 10 displayName: Auto-configure Java applications with the Red Hat build of Cryostat + nextQuickStart: + - configuring-cryostat-jmx introduction: >- Red Hat build of Cryostat is a container-native Java application based on JDK Flight Recorder (JFR). You can use it to monitor the performance of the Java Virtual Machine (JVM) for containerized workloads that run on an OpenShift cluster. diff --git a/config/openshift/cryostat-quickstart-jmx.yaml b/config/openshift/cryostat-quickstart-jmx.yaml index 49427df37..d1144aae9 100644 --- a/config/openshift/cryostat-quickstart-jmx.yaml +++ b/config/openshift/cryostat-quickstart-jmx.yaml @@ -10,6 +10,8 @@ spec: description: Configure your JMX-based Java applications on OpenShift to be profiled and monitored using the Red Hat build of Cryostat. durationMinutes: 10 displayName: Configure JMX-based Java applications with the Red Hat build of Cryostat + nextQuickStart: + - configuring-cryostat-autoconfig introduction: >- Red Hat build of Cryostat is a container-native Java application based on JDK Flight Recorder (JFR). You can use it to monitor the performance of the Java Virtual Machine (JVM) for containerized workloads that run on an OpenShift cluster. From c0004374cd806f76655f85683e8cabd6d6e5c54c Mon Sep 17 00:00:00 2001 From: Andrew Azores Date: Fri, 14 Feb 2025 15:55:44 -0500 Subject: [PATCH 08/11] regen --- ...at-autoconfig_console.openshift.io_v1_consolequickstart.yaml | 2 ++ ...-cryostat-jmx_console.openshift.io_v1_consolequickstart.yaml | 2 ++ bundle/manifests/cryostat-operator.clusterserviceversion.yaml | 2 +- 3 files changed, 5 insertions(+), 1 deletion(-) diff --git a/bundle/manifests/configuring-cryostat-autoconfig_console.openshift.io_v1_consolequickstart.yaml b/bundle/manifests/configuring-cryostat-autoconfig_console.openshift.io_v1_consolequickstart.yaml index 3116ecc41..2d8fac9a6 100644 --- a/bundle/manifests/configuring-cryostat-autoconfig_console.openshift.io_v1_consolequickstart.yaml +++ b/bundle/manifests/configuring-cryostat-autoconfig_console.openshift.io_v1_consolequickstart.yaml @@ -19,6 +19,8 @@ spec: - Alternatively, you can configure your Java applications to allow Java Management Extensions (JMX) connections and use an OpenShift Service for detection and JMX for connectivity. JMX is a standard feature on a JVM with which you can monitor and manage target applications that run on the JVM. You may enable and configure JMX when you start the target application JVM so that Red Hat build of Cryostat can communicate with your JVM over the network using built-in JDK functionality. Follow the **Configure JMX-based Java applications with the Red Hat build of Cryostat** quick start for instructions on that setup. - If you have not yet installed the Red Hat Build of Cryostat Operator, start with the **Get started with the Red Hat build of Cryostat** quick start. - **Note**: The quickstart uses a sample [Quarkus application](https://github.com/quarkusio/quarkus-quickstarts). You can deploy your own application or follow the **Get started with Quarkus using s2i** quick start. + nextQuickStart: + - configuring-cryostat-jmx tasks: - description: | To enable Cryostat Agent instrumentation: diff --git a/bundle/manifests/configuring-cryostat-jmx_console.openshift.io_v1_consolequickstart.yaml b/bundle/manifests/configuring-cryostat-jmx_console.openshift.io_v1_consolequickstart.yaml index fbfcda680..139ecc66c 100644 --- a/bundle/manifests/configuring-cryostat-jmx_console.openshift.io_v1_consolequickstart.yaml +++ b/bundle/manifests/configuring-cryostat-jmx_console.openshift.io_v1_consolequickstart.yaml @@ -19,6 +19,8 @@ spec: - Alternatively, you can configure your Java applications to allow Java Management Extensions (JMX) connections and use an OpenShift Service for detection and JMX for connectivity. JMX is a standard feature on a JVM with which you can monitor and manage target applications that run on the JVM. You may enable and configure JMX when you start the target application JVM so that Red Hat build of Cryostat can communicate with your JVM over the network using built-in JDK functionality. This quick start will explain this JMX-based setup. - If you have not yet installed the Red Hat Build of Cryostat Operator, start with the **Get started with the Red Hat build of Cryostat** quick start. - **Note**: The quickstart uses a sample [Quarkus application](https://github.com/quarkusio/quarkus-quickstarts). You can deploy your own application or follow the **Get started with Quarkus using s2i** quick start. + nextQuickStart: + - configuring-cryostat-autoconfig tasks: - description: | To enable remote JMX connections: diff --git a/bundle/manifests/cryostat-operator.clusterserviceversion.yaml b/bundle/manifests/cryostat-operator.clusterserviceversion.yaml index 5cdbd8493..a325f2193 100644 --- a/bundle/manifests/cryostat-operator.clusterserviceversion.yaml +++ b/bundle/manifests/cryostat-operator.clusterserviceversion.yaml @@ -24,7 +24,7 @@ metadata: capabilities: Seamless Upgrades categories: Monitoring, Developer Tools containerImage: quay.io/cryostat/cryostat-operator:4.1.0-dev - createdAt: "2025-02-08T15:20:55Z" + createdAt: "2025-02-14T20:55:16Z" description: JVM monitoring and profiling tool operatorframework.io/initialization-resource: |- { From cacb2f7597c600092015e4bbe4cf83ff0516567c Mon Sep 17 00:00:00 2001 From: Andrew Azores Date: Sat, 15 Feb 2025 08:20:10 -0500 Subject: [PATCH 09/11] remove ocp-specific bundle additions --- ...ole.openshift.io_v1_consolequickstart.yaml | 69 ------------- ...ole.openshift.io_v1_consolequickstart.yaml | 96 ------------------- 2 files changed, 165 deletions(-) delete mode 100644 bundle/manifests/configuring-cryostat-autoconfig_console.openshift.io_v1_consolequickstart.yaml delete mode 100644 bundle/manifests/configuring-cryostat-jmx_console.openshift.io_v1_consolequickstart.yaml diff --git a/bundle/manifests/configuring-cryostat-autoconfig_console.openshift.io_v1_consolequickstart.yaml b/bundle/manifests/configuring-cryostat-autoconfig_console.openshift.io_v1_consolequickstart.yaml deleted file mode 100644 index 2d8fac9a6..000000000 --- a/bundle/manifests/configuring-cryostat-autoconfig_console.openshift.io_v1_consolequickstart.yaml +++ /dev/null @@ -1,69 +0,0 @@ -apiVersion: console.openshift.io/v1 -kind: ConsoleQuickStart -metadata: - annotations: - capability.openshift.io/name: Console - name: configuring-cryostat-autoconfig -spec: - conclusion: Your Java application has now been configured to be detected by Cryostat. - To profile your Java applications with Cryostat, please follow [this documentation](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/using_cryostat_to_manage_a_jfr_recording/index). - description: Automatically configure your Java applications on OpenShift to be profiled - and monitored using the Red Hat build of Cryostat and Cryostat Agent. - displayName: Auto-configure Java applications with the Red Hat build of Cryostat - durationMinutes: 10 - icon: data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz48c3ZnIGlkPSJMYXllcl8xIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAxMDI0IDEwMjQiPjxkZWZzPjxzdHlsZT4uY2xzLTF7ZmlsbDojZmZmO30uY2xzLTJ7ZmlsbDojMWI0OTY1O30uY2xzLTN7ZmlsbDojOTVjOWU5O30uY2xzLTR7ZmlsbDojNWZhOGQzO308L3N0eWxlPjwvZGVmcz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iNjYxLjc2IDEzOS40OSA2MDcuMzggODUuMTEgNTUwLjQ1IDE0Mi4wNCA1NTAuNDUgMCA0NzMuNTUgMCA0NzMuNTUgMTQyLjA0IDQxNi42MiA4NS4xMSAzNjIuMjQgMTM5LjQ5IDUxMiAyODkuMjYgNjYxLjc2IDEzOS40OSIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMiIgcG9pbnRzPSI1OTcuMzQgNjU5LjgyIDY5OC45MiA2ODcuMDQgNjc3LjY0IDYwNy42MyA3NTcuMDQgNTg2LjM1IDY4Mi42OSA1MTIgNzU3LjA0IDQzNy42NSA2NzcuNjQgNDE2LjM3IDY5OC45MSAzMzYuOTYgNTk3LjM0IDM2NC4xOCA1NzAuMTMgMjYyLjYxIDUxMiAzMjAuNzQgNDUzLjg3IDI2Mi42MSA0MjYuNjYgMzY0LjE4IDMyNS4wOSAzMzYuOTYgMzQ2LjM2IDQxNi4zNyAyNjYuOTYgNDM3LjY1IDM0MS4zMSA1MTIgMjY2Ljk2IDU4Ni4zNSAzNDYuMzYgNjA3LjYzIDMyNS4wOSA2ODcuMDQgNDI2LjY2IDY1OS44MiA0NTMuODcgNzYxLjM5IDUxMiA3MDMuMjYgNTcwLjEzIDc2MS4zOSA1OTcuMzQgNjU5LjgyIi8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjI0Ni4yMyA0NTIuMSAyMTcuMzkgNDgwLjk0IDI0OC43NCA1MTIuMjkgMjE3LjM5IDU0My42NCAyNDYuMjMgNTcyLjQ4IDMwNi40MiA1MTIuMjkgMjQ2LjIzIDQ1Mi4xIi8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9Ijc3Ny43NyA0NTEuNTIgODA2LjYxIDQ4MC4zNiA3NzUuMjYgNTExLjcxIDgwNi42MSA1NDMuMDYgNzc3Ljc3IDU3MS45IDcxNy41OCA1MTEuNzEgNzc3Ljc3IDQ1MS41MiIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMyIgcG9pbnRzPSI0MzEuNDkgNzcyLjQgMzkyLjA5IDc4Mi45NiAzODAuNjIgNzQwLjE0IDMzNy44IDc1MS42MSAzMjcuMjQgNzEyLjIyIDQwOS40NiA2OTAuMTkgNDMxLjQ5IDc3Mi40Ii8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjY5Ny4yNiA3MTEuOTMgNjg2LjcxIDc1MS4zMiA2NDMuODggNzM5Ljg1IDYzMi40MSA3ODIuNjcgNTkzLjAxIDc3Mi4xMSA2MTUuMDQgNjg5LjkgNjk3LjI2IDcxMS45MyIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMyIgcG9pbnRzPSI1OTIuNTEgMjUxLjYgNjMxLjkxIDI0MS4wNCA2NDMuMzggMjgzLjg2IDY4Ni4yIDI3Mi4zOSA2OTYuNzYgMzExLjc4IDYxNC41NCAzMzMuODEgNTkyLjUxIDI1MS42Ii8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjMyNi43NCAzMTIuMDcgMzM3LjI5IDI3Mi42OCAzODAuMTIgMjg0LjE1IDM5MS41OSAyNDEuMzMgNDMwLjk5IDI1MS44OSA0MDguOTYgMzM0LjEgMzI2Ljc0IDMxMi4wNyIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtNCIgcG9pbnRzPSIyNjQuMjggMTk2LjA1IDE5MCAyMTUuOTUgMjEwLjgzIDI5My43MiA4Ny44MiAyMjIuNyA0OS4zNyAyODkuMyAxNzIuMzggMzYwLjMyIDk0LjYxIDM4MS4xNiAxMTQuNTIgNDU1LjQ1IDMxOS4xIDQwMC42MyAyNjQuMjggMTk2LjA1Ii8+PHBvbHlnb24gY2xhc3M9ImNscy00IiBwb2ludHM9IjExNC41MiA1NjguNTYgOTQuNjEgNjQyLjg0IDE3Mi4zOCA2NjMuNjggNDkuMzcgNzM0LjcgODcuODIgODAxLjMgMjEwLjgzIDczMC4yOCAxOTAgODA4LjA1IDI2NC4yOCA4MjcuOTUgMzE5LjEgNjIzLjM3IDExNC41MiA1NjguNTYiLz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iMzYyLjI0IDg4NC41MSA0MTYuNjIgOTM4Ljg5IDQ3My41NSA4ODEuOTYgNDczLjU1IDEwMjQgNTUwLjQ1IDEwMjQgNTUwLjQ1IDg4MS45NiA2MDcuMzggOTM4Ljg5IDY2MS43NiA4ODQuNTEgNTEyIDczNC43NCAzNjIuMjQgODg0LjUxIi8+PHBvbHlnb24gY2xhc3M9ImNscy00IiBwb2ludHM9Ijc1OS43MiA4MjcuOTUgODM0IDgwOC4wNSA4MTMuMTcgNzMwLjI4IDkzNi4xOCA4MDEuMyA5NzQuNjMgNzM0LjcgODUxLjYyIDY2My42OCA5MjkuMzkgNjQyLjg0IDkwOS40OCA1NjguNTUgNzA0LjkgNjIzLjM3IDc1OS43MiA4MjcuOTUiLz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iOTA5LjQ4IDQ1NS40NCA5MjkuMzkgMzgxLjE2IDg1MS42MiAzNjAuMzIgOTc0LjYzIDI4OS4zIDkzNi4xOCAyMjIuNyA4MTMuMTcgMjkzLjcyIDgzNCAyMTUuOTUgNzU5LjcyIDE5Ni4wNSA3MDQuOSA0MDAuNjMgOTA5LjQ4IDQ1NS40NCIvPjxwYXRoIGNsYXNzPSJjbHMtMSIgZD0iTTUxMi41NCw1NzkuNDdjLTM3LjQ3LDAtNjcuOTYtMzAuNDktNjcuOTYtNjcuOTZzMzAuNDktNjcuOTYsNjcuOTYtNjcuOTZjMjUuMTEsMCw0Ny4wNiwxMy42OSw1OC44MiwzNGw2OS4xNy0zOS43Ni0xMjguNTMtNzQuMjEtMTI4LjUzLDc0LjIxdjE0OC40MmwxMjguNTMsNzQuMjEsMTI4LjUzLTc0LjIxLTY5LjE3LTQwLjczYy0xMS43NywyMC4zLTMzLjcyLDMzLjk5LTU4LjgyLDMzLjk5WiIvPjwvc3ZnPgo= - introduction: |- - Red Hat build of Cryostat is a container-native Java application based on JDK Flight Recorder (JFR). You can use it to monitor the performance of the Java Virtual Machine (JVM) for containerized workloads that run on an OpenShift cluster. - - To enable Cryostat to gather, store, and analyze Java Flight Recorder (JFR) data about target applications that run on Java Virtual Machine (JVM)s, you must configure the applications so that Cryostat can detect and connect to them. - - You can use Red Hat build of Cryostat Operator to automatically configure your target application to use the Cryostat Agent to register with a specific Cryostat instance and provide HTTP-based connectivity by following the **Auto-configure Java applications with the Red Hat build of Cryostat** quick start. - - Alternatively, you can configure your Java applications to allow Java Management Extensions (JMX) connections and use an OpenShift Service for detection and JMX for connectivity. JMX is a standard feature on a JVM with which you can monitor and manage target applications that run on the JVM. You may enable and configure JMX when you start the target application JVM so that Red Hat build of Cryostat can communicate with your JVM over the network using built-in JDK functionality. Follow the **Configure JMX-based Java applications with the Red Hat build of Cryostat** quick start for instructions on that setup. - - If you have not yet installed the Red Hat Build of Cryostat Operator, start with the **Get started with the Red Hat build of Cryostat** quick start. - - **Note**: The quickstart uses a sample [Quarkus application](https://github.com/quarkusio/quarkus-quickstarts). You can deploy your own application or follow the **Get started with Quarkus using s2i** quick start. - nextQuickStart: - - configuring-cryostat-jmx - tasks: - - description: | - To enable Cryostat Agent instrumentation: - 1. In the main navigation, click the dropdown menu and select **Administrator**. - 1. In the navigation menu, click **Workloads > Deployments**. - 1. Click on the quarkus-quickstarts deployment name (or your application's deployment name). - 1. Click **YAML** - Alternatively, - 1. In the main navigation, click the dropdown menu and select **Developer**. - 1. In the navigation menu, click **Topology**. - 1. Click on the quarkus-quickstarts deployment (or your application's deployment). - 1. Click **Actions > Edit Deployment**. - 1. Click **Configure via: > YAML view**. - Then, - 1. In the text editor, add the following labels to the `.spec.template.metadata.labels` section: - - - **Name**: `cryostat.io/name` - - **Value**: Set this to the name of your Cryostat Custom Resource instance. - - **Name**: `cryostat.io/namespace` - - **Value**: Set this to the installation namespace of your Cryostat Custom Resource instance. - - 1. Click **Save.** - review: - failedTaskHelp: This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/3/html/getting_started_with_cryostat/configuring_java_applications#working_with_cryostat_agent) - about this topic. - instructions: | - #### Click **Reload** at the bottom of the **YAML** tab. - Do you see a the expected labels under the `.spec.template.metadata.labels`? - title: Enable **Cryostat Agent instrumentation** on your Java Application - - description: | - View your Java application as a target in the Red Hat build of Cryostat web application: - 1. In the main navigation, click the dropdown menu and select **Developer**. - 1. In the navigation menu, click **Topology**. - 1. The external link icon on **cryostat-sample deployment** represents the route URL. - 1. Click the external link icon to open the URL and run the Cryostat web application in a new browser tab. - 1. Enter your Red Hat OpenShift credentials to log in to the Cryostat web application. - 1. In the web application, click **Recordings** in the navigation menu. - 1. View quarkus-quickstarts (or your deployed application) in the **Targets** list. - review: - failedTaskHelp: This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications) - about this topic. - instructions: |- - #### Verify your Java application is running on Red Hat build of Cryostat web application: - - Did the Cryostat web application open in a separate browser window? - title: View your Java Application as a target in Cryostat diff --git a/bundle/manifests/configuring-cryostat-jmx_console.openshift.io_v1_consolequickstart.yaml b/bundle/manifests/configuring-cryostat-jmx_console.openshift.io_v1_consolequickstart.yaml deleted file mode 100644 index 139ecc66c..000000000 --- a/bundle/manifests/configuring-cryostat-jmx_console.openshift.io_v1_consolequickstart.yaml +++ /dev/null @@ -1,96 +0,0 @@ -apiVersion: console.openshift.io/v1 -kind: ConsoleQuickStart -metadata: - annotations: - capability.openshift.io/name: Console - name: configuring-cryostat-jmx -spec: - conclusion: Your Java application has now been configured to be detected by Cryostat. - To profile your Java applications with Cryostat, please follow [this documentation](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/using_cryostat_to_manage_a_jfr_recording/index). - description: Configure your JMX-based Java applications on OpenShift to be profiled - and monitored using the Red Hat build of Cryostat. - displayName: Configure JMX-based Java applications with the Red Hat build of Cryostat - durationMinutes: 10 - icon: data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz48c3ZnIGlkPSJMYXllcl8xIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAxMDI0IDEwMjQiPjxkZWZzPjxzdHlsZT4uY2xzLTF7ZmlsbDojZmZmO30uY2xzLTJ7ZmlsbDojMWI0OTY1O30uY2xzLTN7ZmlsbDojOTVjOWU5O30uY2xzLTR7ZmlsbDojNWZhOGQzO308L3N0eWxlPjwvZGVmcz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iNjYxLjc2IDEzOS40OSA2MDcuMzggODUuMTEgNTUwLjQ1IDE0Mi4wNCA1NTAuNDUgMCA0NzMuNTUgMCA0NzMuNTUgMTQyLjA0IDQxNi42MiA4NS4xMSAzNjIuMjQgMTM5LjQ5IDUxMiAyODkuMjYgNjYxLjc2IDEzOS40OSIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMiIgcG9pbnRzPSI1OTcuMzQgNjU5LjgyIDY5OC45MiA2ODcuMDQgNjc3LjY0IDYwNy42MyA3NTcuMDQgNTg2LjM1IDY4Mi42OSA1MTIgNzU3LjA0IDQzNy42NSA2NzcuNjQgNDE2LjM3IDY5OC45MSAzMzYuOTYgNTk3LjM0IDM2NC4xOCA1NzAuMTMgMjYyLjYxIDUxMiAzMjAuNzQgNDUzLjg3IDI2Mi42MSA0MjYuNjYgMzY0LjE4IDMyNS4wOSAzMzYuOTYgMzQ2LjM2IDQxNi4zNyAyNjYuOTYgNDM3LjY1IDM0MS4zMSA1MTIgMjY2Ljk2IDU4Ni4zNSAzNDYuMzYgNjA3LjYzIDMyNS4wOSA2ODcuMDQgNDI2LjY2IDY1OS44MiA0NTMuODcgNzYxLjM5IDUxMiA3MDMuMjYgNTcwLjEzIDc2MS4zOSA1OTcuMzQgNjU5LjgyIi8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjI0Ni4yMyA0NTIuMSAyMTcuMzkgNDgwLjk0IDI0OC43NCA1MTIuMjkgMjE3LjM5IDU0My42NCAyNDYuMjMgNTcyLjQ4IDMwNi40MiA1MTIuMjkgMjQ2LjIzIDQ1Mi4xIi8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9Ijc3Ny43NyA0NTEuNTIgODA2LjYxIDQ4MC4zNiA3NzUuMjYgNTExLjcxIDgwNi42MSA1NDMuMDYgNzc3Ljc3IDU3MS45IDcxNy41OCA1MTEuNzEgNzc3Ljc3IDQ1MS41MiIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMyIgcG9pbnRzPSI0MzEuNDkgNzcyLjQgMzkyLjA5IDc4Mi45NiAzODAuNjIgNzQwLjE0IDMzNy44IDc1MS42MSAzMjcuMjQgNzEyLjIyIDQwOS40NiA2OTAuMTkgNDMxLjQ5IDc3Mi40Ii8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjY5Ny4yNiA3MTEuOTMgNjg2LjcxIDc1MS4zMiA2NDMuODggNzM5Ljg1IDYzMi40MSA3ODIuNjcgNTkzLjAxIDc3Mi4xMSA2MTUuMDQgNjg5LjkgNjk3LjI2IDcxMS45MyIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtMyIgcG9pbnRzPSI1OTIuNTEgMjUxLjYgNjMxLjkxIDI0MS4wNCA2NDMuMzggMjgzLjg2IDY4Ni4yIDI3Mi4zOSA2OTYuNzYgMzExLjc4IDYxNC41NCAzMzMuODEgNTkyLjUxIDI1MS42Ii8+PHBvbHlnb24gY2xhc3M9ImNscy0zIiBwb2ludHM9IjMyNi43NCAzMTIuMDcgMzM3LjI5IDI3Mi42OCAzODAuMTIgMjg0LjE1IDM5MS41OSAyNDEuMzMgNDMwLjk5IDI1MS44OSA0MDguOTYgMzM0LjEgMzI2Ljc0IDMxMi4wNyIvPjxwb2x5Z29uIGNsYXNzPSJjbHMtNCIgcG9pbnRzPSIyNjQuMjggMTk2LjA1IDE5MCAyMTUuOTUgMjEwLjgzIDI5My43MiA4Ny44MiAyMjIuNyA0OS4zNyAyODkuMyAxNzIuMzggMzYwLjMyIDk0LjYxIDM4MS4xNiAxMTQuNTIgNDU1LjQ1IDMxOS4xIDQwMC42MyAyNjQuMjggMTk2LjA1Ii8+PHBvbHlnb24gY2xhc3M9ImNscy00IiBwb2ludHM9IjExNC41MiA1NjguNTYgOTQuNjEgNjQyLjg0IDE3Mi4zOCA2NjMuNjggNDkuMzcgNzM0LjcgODcuODIgODAxLjMgMjEwLjgzIDczMC4yOCAxOTAgODA4LjA1IDI2NC4yOCA4MjcuOTUgMzE5LjEgNjIzLjM3IDExNC41MiA1NjguNTYiLz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iMzYyLjI0IDg4NC41MSA0MTYuNjIgOTM4Ljg5IDQ3My41NSA4ODEuOTYgNDczLjU1IDEwMjQgNTUwLjQ1IDEwMjQgNTUwLjQ1IDg4MS45NiA2MDcuMzggOTM4Ljg5IDY2MS43NiA4ODQuNTEgNTEyIDczNC43NCAzNjIuMjQgODg0LjUxIi8+PHBvbHlnb24gY2xhc3M9ImNscy00IiBwb2ludHM9Ijc1OS43MiA4MjcuOTUgODM0IDgwOC4wNSA4MTMuMTcgNzMwLjI4IDkzNi4xOCA4MDEuMyA5NzQuNjMgNzM0LjcgODUxLjYyIDY2My42OCA5MjkuMzkgNjQyLjg0IDkwOS40OCA1NjguNTUgNzA0LjkgNjIzLjM3IDc1OS43MiA4MjcuOTUiLz48cG9seWdvbiBjbGFzcz0iY2xzLTQiIHBvaW50cz0iOTA5LjQ4IDQ1NS40NCA5MjkuMzkgMzgxLjE2IDg1MS42MiAzNjAuMzIgOTc0LjYzIDI4OS4zIDkzNi4xOCAyMjIuNyA4MTMuMTcgMjkzLjcyIDgzNCAyMTUuOTUgNzU5LjcyIDE5Ni4wNSA3MDQuOSA0MDAuNjMgOTA5LjQ4IDQ1NS40NCIvPjxwYXRoIGNsYXNzPSJjbHMtMSIgZD0iTTUxMi41NCw1NzkuNDdjLTM3LjQ3LDAtNjcuOTYtMzAuNDktNjcuOTYtNjcuOTZzMzAuNDktNjcuOTYsNjcuOTYtNjcuOTZjMjUuMTEsMCw0Ny4wNiwxMy42OSw1OC44MiwzNGw2OS4xNy0zOS43Ni0xMjguNTMtNzQuMjEtMTI4LjUzLDc0LjIxdjE0OC40MmwxMjguNTMsNzQuMjEsMTI4LjUzLTc0LjIxLTY5LjE3LTQwLjczYy0xMS43NywyMC4zLTMzLjcyLDMzLjk5LTU4LjgyLDMzLjk5WiIvPjwvc3ZnPgo= - introduction: |- - Red Hat build of Cryostat is a container-native Java application based on JDK Flight Recorder (JFR). You can use it to monitor the performance of the Java Virtual Machine (JVM) for containerized workloads that run on an OpenShift cluster. - - To enable Cryostat to gather, store, and analyze Java Flight Recorder (JFR) data about target applications that run on Java Virtual Machine (JVM)s, you must configure the applications so that Cryostat can detect and connect to them. - - You can use Red Hat build of Cryostat Operator to automatically configure your target application to use the Cryostat Agent to register with a specific Cryostat instance and provide HTTP-based connectivity by following the **Auto-configure Java applications with the Red Hat build of Cryostat** quick start. - - Alternatively, you can configure your Java applications to allow Java Management Extensions (JMX) connections and use an OpenShift Service for detection and JMX for connectivity. JMX is a standard feature on a JVM with which you can monitor and manage target applications that run on the JVM. You may enable and configure JMX when you start the target application JVM so that Red Hat build of Cryostat can communicate with your JVM over the network using built-in JDK functionality. This quick start will explain this JMX-based setup. - - If you have not yet installed the Red Hat Build of Cryostat Operator, start with the **Get started with the Red Hat build of Cryostat** quick start. - - **Note**: The quickstart uses a sample [Quarkus application](https://github.com/quarkusio/quarkus-quickstarts). You can deploy your own application or follow the **Get started with Quarkus using s2i** quick start. - nextQuickStart: - - configuring-cryostat-autoconfig - tasks: - - description: | - To enable remote JMX connections: - 1. In the main navigation, click the dropdown menu and select **Administrator**. - 1. In the navigation menu, click **Workloads > Deployments**. - 1. Click on the quarkus-quickstarts deployment name (or your application's deployment name). - 1. Click **Environment.** - 1. In the **Single values (env)** section, add the following environment variable: - - - **Name**: `JAVA_OPTS_APPEND` - - **Value**: - ``` - -Dcom.sun.management.jmxremote.port=9091 - -Dcom.sun.management.jmxremote.authenticate=false - -Dcom.sun.management.jmxremote.ssl=false - ``` - - Note: This method enables remote JMX without authentication. For details on configuring authentication with SSL/TLS for Remote JMX, see [Configuring Java applications](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications). - - 1. Click **Save.** - review: - failedTaskHelp: This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications) - about this topic. - instructions: | - #### Click **Reload** at the bottom of the **Environment** tab. - Do you see a **single values entry** for **`JAVA_OPTS_APPEND`**? - title: Enable **Remote Java Management Extensions (JMX) connections** on your - Java Application - - description: | - To update Red Hat OpenShift Service with the remote JMX port: - 1. In the main navigation, click the dropdown menu and select **Administrator**. - 1. In the navigation menu, click **Networking > Services**. - 1. Click on the quarkus-quickstarts service name (or your application's service name). - 1. Click the “YAML” tab to open the YAML editor. - 1. In the **spec > ports** section, add a new port for jfr-jmx - - ``` - - name: jfr-jmx - protocol: TCP - port: 9091 - targetPort: 9091 - ``` - - 1. Click **Save**. - review: - failedTaskHelp: This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications) - about this topic. - instructions: | - #### Verify that the service port is added to the sample resource: - 1. In the main navigation, click the dropdown menu and select **Developer**. - 1. In the navigation menu, click **Topology**. - 1. Click on the quarkus-quickstarts deployment name (or your application's service name). - 1. Click on the **Resources** tab. - - Do you see **Service port: jfr-jmx -> Pod port: 9091** in the quarkus-quickstarts service? - title: Updating Red Hat OpenShift Service with the remote JMX port - - description: | - View your Java application as a target in the Red Hat build of Cryostat web application: - 1. In the main navigation, click the dropdown menu and select **Developer**. - 1. In the navigation menu, click **Topology**. - 1. The external link icon on **cryostat-sample deployment** represents the route URL. - 1. Click the external link icon to open the URL and run the Cryostat web application in a new browser tab. - 1. Enter your Red Hat OpenShift credentials to log in to the Cryostat web application. - 1. In the web application, click **Recordings** in the navigation menu. - 1. View quarkus-quickstarts (or your deployed application) in the **Targets** list. - review: - failedTaskHelp: This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications) - about this topic. - instructions: |- - #### Verify your Java application is running on Red Hat build of Cryostat web application: - - Did the Cryostat web application open in a separate browser window? - title: View your Java Application as a target in Cryostat From b3b2306190731f1a169de70ceb458e99ce879142 Mon Sep 17 00:00:00 2001 From: Andrew Azores Date: Sat, 15 Feb 2025 08:20:39 -0500 Subject: [PATCH 10/11] fixup! remove ocp-specific bundle additions --- bundle/manifests/cryostat-operator.clusterserviceversion.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bundle/manifests/cryostat-operator.clusterserviceversion.yaml b/bundle/manifests/cryostat-operator.clusterserviceversion.yaml index a325f2193..6888dfe49 100644 --- a/bundle/manifests/cryostat-operator.clusterserviceversion.yaml +++ b/bundle/manifests/cryostat-operator.clusterserviceversion.yaml @@ -24,7 +24,7 @@ metadata: capabilities: Seamless Upgrades categories: Monitoring, Developer Tools containerImage: quay.io/cryostat/cryostat-operator:4.1.0-dev - createdAt: "2025-02-14T20:55:16Z" + createdAt: "2025-02-05T19:21:11Z" description: JVM monitoring and profiling tool operatorframework.io/initialization-resource: |- { From 254453451def6218920e24a45853107de563ed7e Mon Sep 17 00:00:00 2001 From: Andrew Azores Date: Wed, 19 Feb 2025 16:45:02 -0500 Subject: [PATCH 11/11] v4 doc --- config/openshift/cryostat-quickstart-autoconfig.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/openshift/cryostat-quickstart-autoconfig.yaml b/config/openshift/cryostat-quickstart-autoconfig.yaml index c54505cbf..e1c4267c6 100644 --- a/config/openshift/cryostat-quickstart-autoconfig.yaml +++ b/config/openshift/cryostat-quickstart-autoconfig.yaml @@ -60,7 +60,7 @@ spec: 1. Click **Save.** review: failedTaskHelp: >- - This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/3/html/getting_started_with_cryostat/configuring_java_applications#working_with_cryostat_agent) + This task isn't verified yet. Try the task again, or [read more](https://docs.redhat.com/en/documentation/red_hat_build_of_cryostat/4/html/getting_started_with_cryostat/configuring_java_applications#working_with_cryostat_agent) about this topic. instructions: > #### Click **Reload** at the bottom of the **YAML** tab.