Setting Up the yc-360 Script

• Create a directory for yc-360 script

  mkdir -p /opt/workspace/yc-360
cd /opt/workspace/yc-360 Copy code

• Download the latest yc-360 script

  wget https://tier1app.com/dist/ycrash/yc-360-latest.zip Copy code

• Extract the downloaded zip file

  unzip yc-360-latest.zip Copy code

• After unzipping, navigate to the Mac directory. Inside this directory, select the yc-360 script that matches your server's architecture (amd64 or arm64).

• Create YAML Configuration File: Create a YAML configuration file named yc-config.yaml in same directory where you have "yc-360" script and add the following content:

  version: '1'
options:
   k: Testing@f05b4d6c-4aad-4d37-b47b-92b809841339
   s: https://tst-srv-jdk11.ycrash.io/
   j: {JAVA_HOME}
   a: {APPLICATION_NAME} Copy code

  Replace the placeholders in the YAML configuration file with your actual values:

  • {JAVA_HOME}: The directory path where Java is installed on your system.
  • {APPLICATION_NAME}: Friendly name for the application (displayed in the yCrash dashboard).

  For a full list of arguments, refer to the All yc-360 Script Arguments page.

• Execute: Run the script with the following command:

  ./yc -c yc-config.yaml -p {PID} Copy code

INFO:

• {PID}: This is the process ID of your Java application. Not sure how to find it? Learn here. Alternatively, you can pass Unique Token that will uniquely identify the process. What is Unique Token?

IMPORTANT TIP:

• The yc-360 script must be executed with the same user privileges as the Java application. For example, if the application runs under the 'tomcat-user' user, yc-360 script must also be executed by 'tomcat-user' user.
• To detect memory-related issues, GC logging must be enabled for your application. You can enable GC logging by using the JVM arguments listed here

• Download: Download the latest version of the yc-360 script from here.

• Create YAML Configuration File: Create a YAML configuration file named yc-config.yaml in same directory where you have "yc-360" script and add the following content:

  version: '1'
options:
   k: Testing@f05b4d6c-4aad-4d37-b47b-92b809841339
   s: https://tst-srv-jdk11.ycrash.io/
   j: {JAVA_HOME}
   a: {APPLICATION_NAME} Copy code

  Replace the placeholders in the YAML configuration file with your actual values:

  • {JAVA_HOME}: The directory path where Java is installed on your system.
  • {APPLICATION_NAME}: Friendly name for the application (displayed in the yCrash dashboard).

  For a full list of arguments, refer to the All yc-360 Script Arguments page.

• Execute: Run the script with the following command:

  .\yc -c yc-config.yaml -p {PID} Copy code

INFO:

• {PID}: This is the process ID of your Java application. Not sure how to find it? Learn here. Alternatively, you can pass Unique Token that will uniquely identify the process. What is Unique Token?

IMPORTANT TIP:

• The yc-360 script must be executed with the same user privileges as the Java application. For example, if the application runs under the 'tomcat-user' user, yc-360 script must also be executed by 'tomcat-user' user.
• To detect memory-related issues, GC logging must be enabled for your application. You can enable GC logging by using the JVM arguments listed here

To monitor and troubleshoot Java applications running inside Docker containers, the yc-360 script can be deployed in three flexible ways. Depending on your architecture and security preferences, you can choose the method that best fits your needs. Learn more on the Deployment Options in Docker page.

The yc-360 script can be seamlessly integrated into your Kubernetes environment to monitor and analyze Java applications running in pods. You can choose the approach best suits your setup. Learn more on the Deployment Options in Kubernetes page.

The yc-360 script can be seamlessly integrated into your OpenShift environment to monitor and analyze Java applications running in pods. To learn more, please visit the Run yc-360 Script in OpenShift page.