Skip to content

Commit 247e8f2

Browse files
authored
Updated Readme.md file
1 parent f0992b9 commit 247e8f2

File tree

1 file changed

+78
-1
lines changed

1 file changed

+78
-1
lines changed

README.md

Lines changed: 78 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,78 @@
1-
# ycrash-agent
1+
# ycrash-agent
2+
3+
## What does the yCrash agent do?
4+
5+
<img src="/docs/images/360-degree-data.png" width="600" height="300" />
6+
7+
yCrash agent is a simple Golang script that captures 16 different artifacts from your application in a **pristine** manner. These artifacts will be highly useful to troubleshoot performance problems. Below is the list of artifacts captured:
8+
9+
1. Garbage collection log
10+
2. Thread dump
11+
3. Heap dump
12+
4. Heap substitute
13+
5. top
14+
6. ps
15+
7. top -H
16+
8. Disk usage
17+
9. dmesg
18+
10. netstat
19+
11. ping
20+
12. vmstat
21+
13. iostat
22+
14. Kernel parameters
23+
15. Application Log
24+
16. Metadata
25+
26+
## How to run the yCrash agent?
27+
28+
1. Download latest yCrash agent script from [this](https://tier1app.com/dist/ycrash/yc-agent-latest.zip) location
29+
2. Unzip the downloaded ```yc-agent-latest.zip``` file. (Say you are unzipping in '/opt/workspace/yc-agent-latest' folder)
30+
3. In the unzipped folder you will find two files:
31+
32+
a) ```yc``` - If you are running on Unix/Linux/Mac, then use this file.
33+
b) ```yc.exe``` - If you are running on Windows, then use this file.
34+
35+
You need to invoke yCrash script with following arguments:
36+
37+
```
38+
./yc -j {JAVA_HOME} -onlyCapture -p {PID} -hd
39+
```
40+
41+
Where,
42+
43+
**JAVA_HOME** is the home directory where JDK is installed
44+
45+
**PID** is the target JVM's process ID
46+
47+
**Example:**
48+
49+
```
50+
./yc -j /usr/java/jdk1.8.0_141 -onlyCapture -p 15326 -hd
51+
```
52+
53+
When you pass the above arguments, yCrash script will capture all the application level and system level artifacts/logs from the server from the target JVM & host for analysis. Captured artifacts will be compressed into a zip file and stored in the current directory where the above command was executed. The zip file will have the name in the format: 'yc-YYYY-MM-DDTHH-mm-ss.zip'.
54+
55+
**Example:** 'yc-2021-03-06T14-02-42.zip'.
56+
57+
## How to analyze the artifacts generated by the yCrash agent?
58+
59+
You can analyze the artifacts captured by yCrash agent either manually or through [yCrash server](https://ycrash.io/). yCrash server analyzes all the captured data and generates a root cause analysis report instantly. You can use the [Bundle upload](https://docs.ycrash.io/ycrash-features/bundle-upload.html#step-1-go-to-upload-incident-form) feature in the yCrash server to analyze the captured 360-degree data.
60+
61+
### Advanced launch modes
62+
63+
You can launch yCrash agent in following [3 different modes](https://docs.ycrash.io/ycrash-agent/launch-modes.html#launch-modes):
64+
65+
1. **On-demand Mode:** In this mode you can directly transmit 360-degree artifacts from your server to yCrash server for analysis.
66+
2. **API Mode:** In this mode you can integrate yCrash agent with your current monitoring tools such as AppDynamics, New Relic, Dynatrace, …
67+
3. **M3 (Micro-metrics Monitoring) mode:** In this mode, yCrash agent proactively detect performance outages much earlier before it surfaces
68+
69+
### How to build the agent?
70+
71+
Please refer to any one of the following links if you want to build the ycrash agent in that corresponding operating system:
72+
73+
1. Build yc agent in [Windows](/docs/Build%20yc%20agent%20in%20Windows.pdf)
74+
2. Build yc agent in [Alpine](/docs/build-yc-agent-alpine.md)
75+
3. Build yc agent in [Centos](/docs/build-yc-agent-centos.md)
76+
4. Build yc agent in [Linux](/docs/build-yc-agent-linux.md)
77+
5. Build yc agent in [MacOS](/docs/build-yc-agent-macos.md)
78+
6. Build yc agent in [Ubuntu](/docs/build-yc-agent-ubuntu.md)

0 commit comments

Comments
 (0)