Skip to content

Commit a46a66c

Browse files
author
Alagappan21
committed
font style issue resolved
1 parent 2744b92 commit a46a66c

File tree

1 file changed

+21
-21
lines changed

1 file changed

+21
-21
lines changed

‎README.md‎

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -42,34 +42,34 @@
4242
It's easy to get started with the yc-360 script. Just follow the simple steps given below. In a matter of seconds, you’ll be able to trigger the script and collect all the critical artifacts needed for troubleshooting.
4343

4444
<details>
45-
<summary><strong>Linux</storng></summary></br>
45+
<summary><strong>Linux</strong></summary></br>
4646

4747
<strong>1. Download:</strong> Download the latest version of the yc-360 script from [here](https://tier1app.com/dist/ycrash/yc-360-latest.zip)
4848

49-
<storng>2. Extract:</storng> Unzip the package and navigate to the linux directory:
49+
<strong>2. Extract:</strong> Unzip the package and navigate to the linux directory:
5050

5151
```sh
5252
unzip yc-360-latest.zip
5353
cd linux
5454
```
5555

56-
<storng>3. Execute yc-360 Script:</storng> Run the script with your target application's process ID:
56+
<strong>3. Execute yc-360 Script:</strong> Run the script with your target application's process ID:
5757

5858
When you execute the below command, the yc-360 script will capture all the artifacts/logs from the target JVM & host for analysis. Captured artifacts will be compressed into a zip file and stored in the directory where the above command was executed. The zip file will have the name in the format: 'yc-YYYY-MM-DDTHH-mm-ss.zip'. **Example**: 'yc-2024-09-23T14-02-42.zip'.
5959

6060
```sh
6161
./yc -onlyCapture -p {PID} -j {JAVA_HOME} -a {APPLICATION_NAME}
6262
```
6363

64-
<storng>INFO:</storng>
64+
<strong>INFO:</strong>
6565

6666
+ `{PID}`: This is the process ID of your Java application. Not sure how to find process Id? [Learn here](https://docs.ycrash.io/yc-360/faq/identifying-process.html). Alternatively, you can pass Unique Token that will uniquely identify the process in container. [What is Unique Token?](https://docs.ycrash.io/yc-360/faq/what-is-unique-token-in-process.html)
6767

6868
+ `{JAVA_HOME}`: The directory path where Java is installed in your environment.
6969

7070
+ `{APPLICATION_NAME}`: Friendly name for the application (displayed in the yCrash dashboard).
7171

72-
<storng>IMPORTANT TIP:<storng>
72+
<strong>IMPORTANT TIP:<strong>
7373

7474
+ 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.
7575

@@ -79,34 +79,34 @@ When you execute the below command, the yc-360 script will capture all the artif
7979

8080
</details>
8181
<details>
82-
<summary><strong>MacOS</storng></summary></br>
82+
<summary><strong>MacOS</strong></summary></br>
8383

84-
<storng>1. Download:</storng> Download the latest version of the yc-360 script from [here](https://tier1app.com/dist/ycrash/yc-360-latest.zip).
84+
<strong>1. Download:</strong> Download the latest version of the yc-360 script from [here](https://tier1app.com/dist/ycrash/yc-360-latest.zip).
8585

86-
<storng>2. Extract:</storng> Unzip the package and navigate to the mac directory:
86+
<strong>2. Extract:</strong> Unzip the package and navigate to the mac directory:
8787

8888
```sh
8989
unzip yc-360-latest.zip
9090
cd mac
9191
```
9292

93-
<storng>3. Execute yc-360 Script:</storng> Run the script with your target application's process ID:
93+
<strong>3. Execute yc-360 Script:</strong> Run the script with your target application's process ID:
9494

9595
When you execute the below command, the yc-360 script will capture all the artifacts/logs from the target JVM & host for analysis. Captured artifacts will be compressed into a zip file and stored in the directory where the above command was executed. The zip file will have the name in the format: 'yc-YYYY-MM-DDTHH-mm-ss.zip'. **Example**: 'yc-2024-09-23T14-02-42.zip'.
9696

9797
```sh
9898
./yc -onlyCapture -p {PID} -j {JAVA_HOME} -a {APPLICATION_NAME}
9999
```
100100

101-
<storng>INFO:</storng>
101+
<strong>INFO:</strong>
102102

103103
+ `{PID}`: This is the process ID of your Java application. Not sure how to find process Id? [Learn here](https://docs.ycrash.io/yc-360/faq/identifying-process.html). Alternatively, you can pass Unique Token that will uniquely identify the process in container. [What is Unique Token?](https://docs.ycrash.io/yc-360/faq/what-is-unique-token-in-process.html)
104104

105105
+ `{JAVA_HOME}`: The directory path where Java is installed in your environment.
106106

107107
+ `{APPLICATION_NAME}`: Friendly name for the application (displayed in the yCrash dashboard).
108108

109-
<storng>IMPORTANT TIP:</storng>
109+
<strong>IMPORTANT TIP:</strong>
110110

111111
+ 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.
112112

@@ -117,33 +117,33 @@ When you execute the below command, the yc-360 script will capture all the artif
117117
</details>
118118

119119
<details>
120-
<summary><strong>Windows</storng></summary></br>
120+
<summary><strong>Windows</strong></summary></br>
121121

122-
<storng>1. Download:</storng> Download the latest version of the yc-360 script from [here](https://tier1app.com/dist/ycrash/yc-360-latest.zip).
122+
<strong>1. Download:</strong> Download the latest version of the yc-360 script from [here](https://tier1app.com/dist/ycrash/yc-360-latest.zip).
123123

124-
<storng>2. Extract:</storng> Unzip the package and navigate to the windows directory:
124+
<strong>2. Extract:</strong> Unzip the package and navigate to the windows directory:
125125

126126
```
127127
cd windows
128128
```
129129

130-
<storng>3. Execute yc-360 Script:</storng> Run the script with your target application's process ID:
130+
<strong>3. Execute yc-360 Script:</strong> Run the script with your target application's process ID:
131131

132132
When you execute the below command, the yc-360 script will capture all the artifacts/logs from the target JVM & host for analysis. Captured artifacts will be compressed into a zip file and stored in the directory where the above command was executed. The zip file will have the name in the format: 'yc-YYYY-MM-DDTHH-mm-ss.zip'. **Example**: 'yc-2024-09-23T14-02-42.zip'.
133133

134134
```sh
135135
.\yc -onlyCapture -p {PID} -j {JAVA_HOME} -a {APPLICATION_NAME}
136136
```
137137

138-
<storng>INFO:</storng>
138+
<strong>INFO:</strong>
139139

140140
+ `{PID}`: This is the process ID of your Java application. Not sure how to find process Id? [Learn here](https://docs.ycrash.io/yc-360/faq/identifying-process.html). Alternatively, you can pass Unique Token that will uniquely identify the process in container. [What is Unique Token?](https://docs.ycrash.io/yc-360/faq/what-is-unique-token-in-process.html)
141141

142142
+ `{JAVA_HOME}`: The directory path where Java is installed in your environment.
143143

144144
+ `{APPLICATION_NAME}`: Friendly name for the application (displayed in the yCrash dashboard).
145145

146-
<storng>IMPORTANT TIP:</storng>
146+
<strong>IMPORTANT TIP:</strong>
147147

148148
+ 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.
149149

@@ -153,7 +153,7 @@ When you execute the below command, the yc-360 script will capture all the artif
153153
</details>
154154

155155
<details>
156-
<summary><strong>Docker</storng></summary></br>
156+
<summary><strong>Docker</strong></summary></br>
157157

158158
You can run the yc-360 script in a Docker environment using one of the following approaches, depending on your deployment setup and monitoring preferences:
159159

@@ -165,7 +165,7 @@ You can run the yc-360 script in a Docker environment using one of the following
165165
</details>
166166

167167
<details>
168-
<summary><strong>Kubernetes</storng></summary></br>
168+
<summary><strong>Kubernetes</strong></summary></br>
169169

170170
You can run the yc-360 script in a Kubernetes environment using one of the following approaches, depending on your deployment setup and monitoring preferences:
171171

@@ -175,15 +175,15 @@ You can run the yc-360 script in a Kubernetes environment using one of the follo
175175
</details>
176176

177177
<details>
178-
<summary><strong>OpenShift</storng></summary></br>
178+
<summary><strong>OpenShift</strong></summary></br>
179179

180180
To monitor applications running in OpenShift, deploy the yc-360 script using:
181181

182182
[Run yc-360 Script in Sidecar Container](https://docs.ycrash.io/yc-360/openshift/deployment-options/run-as-sidecar-container.html)– Add yc-360 alongside your application within the pod template.
183183
</details>
184184

185185
<details>
186-
<summary><strong>AWS Fargate</storng></summary></br>
186+
<summary><strong>AWS Fargate</strong></summary></br>
187187

188188
You can run the yc-360 script in an AWS Fargate environment using one of the following approaches, depending on your orchestration platform:
189189

0 commit comments

Comments
 (0)