diff --git a/site/src/site/sphinx/en/perfcounter.md b/site/src/site/sphinx/en/perfcounter.md index b6b5faa04..d1b0ea691 100644 --- a/site/src/site/sphinx/en/perfcounter.md +++ b/site/src/site/sphinx/en/perfcounter.md @@ -1,6 +1,8 @@ perfcounter === +[`perfcounter` online tutorial](https://alibaba.github.io/arthas/arthas-tutorials?language=en&id=command-perfcounter) + > Check the current JVM Perf Counter information. ### Usage diff --git a/site/src/site/sphinx/perfcounter.md b/site/src/site/sphinx/perfcounter.md index 08ea3357a..d8ce0f39b 100644 --- a/site/src/site/sphinx/perfcounter.md +++ b/site/src/site/sphinx/perfcounter.md @@ -1,6 +1,8 @@ perfcounter === +[`perfcounter`在线教程](https://alibaba.github.io/arthas/arthas-tutorials?language=cn&id=command-perfcounter) + > 查看当前JVM的 Perf Counter信息 ### 使用参考 diff --git a/tutorials/katacoda/command-perfcounter-cn/arthas-boot.md b/tutorials/katacoda/command-perfcounter-cn/arthas-boot.md new file mode 100644 index 000000000..d53c8ff8a --- /dev/null +++ b/tutorials/katacoda/command-perfcounter-cn/arthas-boot.md @@ -0,0 +1,16 @@ + + + + +在新的`Terminal 2`里，下载`arthas-boot.jar`，再用`java -jar`命令启动： + +`wget https://alibaba.github.io/arthas/arthas-boot.jar +java -jar arthas-boot.jar --target-ip 0.0.0.0`{{execute T2}} + +`arthas-boot`是`Arthas`的启动程序，它启动后，会列出所有的Java进程，用户可以选择需要诊断的目标进程。 + +选择第一个进程，输入 `1`{{execute T2}} ，再`Enter/回车`： + +Attach成功之后，会打印Arthas LOGO。输入 `help`{{execute T2}} 可以获取到更多的帮助信息。 + +![Arthas Boot](/arthas/scenarios/common-resources/assets/arthas-boot.png) diff --git a/tutorials/katacoda/command-perfcounter-cn/arthas-demo.md b/tutorials/katacoda/command-perfcounter-cn/arthas-demo.md new file mode 100644 index 000000000..f1136e88e --- /dev/null +++ b/tutorials/katacoda/command-perfcounter-cn/arthas-demo.md @@ -0,0 +1,10 @@ + + + + +下载`arthas-demo.jar`，再用`java -jar`命令启动： + +`wget https://alibaba.github.io/arthas/arthas-demo.jar +java -jar arthas-demo.jar`{{execute T1}} + +`arthas-demo`是一个很简单的程序，它随机生成整数，再执行因式分解，把结果打印出来。如果生成的随机数是负数，则会打印提示信息。 diff --git a/tutorials/katacoda/command-perfcounter-cn/finish.md b/tutorials/katacoda/command-perfcounter-cn/finish.md new file mode 100644 index 000000000..b38f92000 --- /dev/null +++ b/tutorials/katacoda/command-perfcounter-cn/finish.md @@ -0,0 +1,12 @@ + +在“perfcounter”中，我们演示了了Arthas的perfcounter命令。如果有更多的技巧或者使用疑问，欢迎在Issue里提出。 + +* Issues: https://github.com/alibaba/arthas/issues +* 文档： https://alibaba.github.io/arthas + + +如果您在使用Arthas，请让我们知道，您的使用对我们非常重要：[查看](https://github.com/alibaba/arthas/issues/111) + +欢迎关注公众号，获取Arthas项目的信息，源码分析，案例实践。 + +![Arthas公众号](/arthas/scenarios/common-resources/assets/qrcode_gongzhonghao.jpg) \ No newline at end of file diff --git a/tutorials/katacoda/command-perfcounter-cn/index.json b/tutorials/katacoda/command-perfcounter-cn/index.json new file mode 100644 index 000000000..c3e47ec96 --- /dev/null +++ b/tutorials/katacoda/command-perfcounter-cn/index.json @@ -0,0 +1,35 @@ +{ + "title": "Arthas perfcounter命令", + "description": "Arthas perfcounter命令", + "difficulty": "精通者", + "time": "10-20 分钟", + "details": { + "steps": [ + { + "title": "Arthas demo", + "text": "arthas-demo.md" + }, + { + "title": "启动arthas-boot", + "text": "arthas-boot.md" + }, + { + "title": "perfcounter命令", + "text": "perfcounter.md" + } + ], + "intro": { + "text": "intro.md" + }, + "finish": { + "text": "finish.md" + } + }, + "environment": { + "uilayout": "terminal" + }, + "backend": { + "imageid": "java", + "environmentsprotocol": "http" + } +} diff --git a/tutorials/katacoda/command-perfcounter-cn/intro.md b/tutorials/katacoda/command-perfcounter-cn/intro.md new file mode 100644 index 000000000..349f7318f --- /dev/null +++ b/tutorials/katacoda/command-perfcounter-cn/intro.md @@ -0,0 +1,23 @@ + + + +![Arthas](https://alibaba.github.io/arthas/_images/arthas.png) + +`Arthas` 是Alibaba开源的Java诊断工具，深受开发者喜爱。在线排查问题，无需重启；动态跟踪Java代码；实时监控JVM状态。 + +`Arthas` 支持JDK 6+，支持Linux/Mac/Windows，采用命令行交互模式，同时提供丰富的 `Tab` 自动补全功能，进一步方便进行问题的定位和诊断。 + +当你遇到以下类似问题而束手无策时，Arthas可以帮助你解决： + +- 这个类从哪个 jar 包加载的？为什么会报各种类相关的 Exception？ +- 我改的代码为什么没有执行到？难道是我没 commit？分支搞错了？ +- 遇到问题无法在线上 debug，难道只能通过加日志再重新发布吗？ +- 线上遇到某个用户的数据处理有问题，但线上同样无法 debug，线下无法重现！ +- 是否有一个全局视角来查看系统的运行状况？ +- 有什么办法可以监控到JVM的实时运行状态？ +- 怎么快速定位应用的热点，生成火焰图？ + +本教程会以一个普通的Spring Boot应用为例，演示perfcounter命令。 + +* Github: https://github.com/alibaba/arthas +* 文档: https://alibaba.github.io/arthas/ diff --git a/tutorials/katacoda/command-perfcounter-cn/perfcounter.md b/tutorials/katacoda/command-perfcounter-cn/perfcounter.md new file mode 100644 index 000000000..6a0a4c549 --- /dev/null +++ b/tutorials/katacoda/command-perfcounter-cn/perfcounter.md @@ -0,0 +1,60 @@ + +查看当前JVM的 Perf Counter信息 + +`perfcounter -h`{{execute T2}} + +```bash + USAGE: + perfcounter [-d] [-h] + + SUMMARY: + Display the perf counter infornation. + + Examples: + perfcounter + perfcounter -d + + WIKI: + https://alibaba.github.io/arthas/perfcounter + + OPTIONS: + -d, --details print all perf counter details + -h, --help this help +``` + +## 使用参考 + +`perfcounter`{{execute T2}} + +```bash +$ perfcounter + java.ci.totalTime 2325637411 + java.cls.loadedClasses 3403 + java.cls.sharedLoadedClasses 0 + java.cls.sharedUnloadedClasses 0 + java.cls.unloadedClasses 0 + java.property.java.version 11.0.4 + java.property.java.vm.info mixed mode + java.property.java.vm.name OpenJDK 64-Bit Server VM + ``` + +可以用-d参数打印更多信息： + +`perfcounter -d`{{execute T2}} + +```bash +$ perfcounter -d + Name Variability Units Value +--------------------------------------------------------------------------------- + java.ci.totalTime Monotonic Ticks 3242526906 + java.cls.loadedClasses Monotonic Events 3404 + java.cls.sharedLoadedClasses Monotonic Events 0 + java.cls.sharedUnloadedClasses Monotonic Events 0 + java.cls.unloadedClasses Monotonic Events 0 +``` + +## 备注: 对于jdk9以上的应用 + +如果没有打印出信息，应用在启动时，加下面的参数： + +`--add-opens java.base/jdk.internal.perf=ALL-UNNAMED --add-exports java.base/jdk.internal.perf=ALL-UNNAMED` diff --git a/tutorials/katacoda/command-perfcounter-en/arthas-boot.md b/tutorials/katacoda/command-perfcounter-en/arthas-boot.md new file mode 100644 index 000000000..29c6aa95e --- /dev/null +++ b/tutorials/katacoda/command-perfcounter-en/arthas-boot.md @@ -0,0 +1,16 @@ + + + + +In the new `Terminal 2`, download `arthas-boot.jar` and start with the `java -jar` command: + +`wget https://alibaba.github.io/arthas/arthas-boot.jar +java -jar arthas-boot.jar --target-ip 0.0.0.0`{{execute T2}} + +`arthas-boot` is the launcher for `Arthas`. It lists all the Java processes, and the user can select the target process to be diagnosed. + +Select the first process, type `1`{{execute T2}} ，then type `Enter`： + +After the Attach is successful, Arthas LOGO is printed. Enter `help`{{execute T2}} for more help. + +![Arthas Boot](/arthas/scenarios/common-resources/assets/arthas-boot.png) diff --git a/tutorials/katacoda/command-perfcounter-en/arthas-demo.md b/tutorials/katacoda/command-perfcounter-en/arthas-demo.md new file mode 100644 index 000000000..7ba2cf1fa --- /dev/null +++ b/tutorials/katacoda/command-perfcounter-en/arthas-demo.md @@ -0,0 +1,11 @@ + + + + +Download `arthas-demo.jar` and start with the `java -jar` command: + +`wget https://alibaba.github.io/arthas/arthas-demo.jar +java -jar arthas-demo.jar`{{execute T1}} + +`arthas-demo` is a very simple program that randomly generates integers, performs factorization, and prints the results. +If the generated random number is negative, a error message will be printed. diff --git a/tutorials/katacoda/command-perfcounter-en/finish.md b/tutorials/katacoda/command-perfcounter-en/finish.md new file mode 100644 index 000000000..7451ffe5b --- /dev/null +++ b/tutorials/katacoda/command-perfcounter-en/finish.md @@ -0,0 +1,8 @@ + +The `perfcounter Tutorial` demonstrates the usage of perfcounter. If you have more tips or questions, please feel free to ask in Issue. + +* Issues: https://github.com/alibaba/arthas/issues +* Documentation: https://alibaba.github.io/arthas + + +If you are using Arthas, please let us know. Your use is very important to us: [View](https://github.com/alibaba/arthas/issues/111) \ No newline at end of file diff --git a/tutorials/katacoda/command-perfcounter-en/index.json b/tutorials/katacoda/command-perfcounter-en/index.json new file mode 100644 index 000000000..909d27492 --- /dev/null +++ b/tutorials/katacoda/command-perfcounter-en/index.json @@ -0,0 +1,35 @@ +{ + "title": "Arthas perfcounter Command", + "description": "Arthas perfcounter Command", + "difficulty": "master", + "time": "10-20 minutes", + "details": { + "steps": [ + { + "title": "Arthas demo", + "text": "arthas-demo.md" + }, + { + "title": "Start arthas-boot", + "text": "arthas-boot.md" + }, + { + "title": "perfcounter Command", + "text": "perfcounter.md" + } + ], + "intro": { + "text": "intro.md" + }, + "finish": { + "text": "finish.md" + } + }, + "environment": { + "uilayout": "terminal" + }, + "backend": { + "imageid": "java", + "environmentsprotocol": "http" + } +} diff --git a/tutorials/katacoda/command-perfcounter-en/intro.md b/tutorials/katacoda/command-perfcounter-en/intro.md new file mode 100644 index 000000000..e5e696e2b --- /dev/null +++ b/tutorials/katacoda/command-perfcounter-en/intro.md @@ -0,0 +1,40 @@ + + + +![Arthas](https://alibaba.github.io/arthas/_images/arthas.png) + +`Arthas` is a Java diagnostic tool open-sourced by Alibaba middleware team. Arthas helps developers in trouble-shooting issues in production environment for Java based applications without modifying code or restarting servers. + +`Arthas` supports JDK 6+, supports Linux/Mac/Windows. + +## Background + +Oftentimes the production system network is inaccessible from local development environment. If issues are encountered in production systems, it is impossible to use IDE to debug the application remotely. What’s even worse, debugging in production environment is unacceptable, as it will suspend all the perfcounters, leading to services downtime. + +Developers could always try to reproduce the same issue on the test/staging environment. However, this is tricky as some issues cannot be reproduced easily in a different environment, or even disappear once restarted. + +And if you’re thinking of adding some logs to your code to help trouble-shoot the issue, you will have to go through the following lifecycle: test, staging, and then to production. Time is money! This approach is inefficient! Worse still, the issue may not be fixed since it might be irreproducible once the JVM is restarted, as described above. + +Arthas is built to solve these issues. A developer can troubleshoot production issues on the fly. No JVM restart, no additional code changes. Arthas works as an observer, that is, it will never suspend your running perfcounters. + +## Key features + +- Check whether a class is loaded? Or where the class is loaded from? (Useful for trouble-shooting jar file conflicts) +- Decompile a class to ensure the code is running as expected. +- Check classloader statistics, e.g. the number of classloaders, the number of classes loaded per classloader, the classloader hierarchy, possible classloader leaks, etc. +- Check the method invocation details, e.g. method parameter, returned values, exceptions and etc. +- Check the stack trace of specified method invocation. This is useful when a developer wants to know the caller of the method. +- Trace the method invocation to find slow sub-invocations. +- Monitor method invocation statistics, e.g. QPS (Query Per Second), RT (Return Time), success rate and etc. +- Monitor system metrics, perfcounter states and CPU usage, GC statistics and etc. +- Supports command line interactive mode, with auto-complete feature enabled. +- Supports telnet and WebSocket, which enables both local and remote diagnostics with command line and browsers. +- Supports profiler/Flame Graph +- Supports JDK 6+ +- Supports Linux/Mac/Windows + +This tutorial takes a normal Spring Boot application as an example to demonstrate the the usage of perfcounter. + +* Github: https://github.com/alibaba/arthas +* Docs: https://alibaba.github.io/arthas/ + diff --git a/tutorials/katacoda/command-perfcounter-en/perfcounter.md b/tutorials/katacoda/command-perfcounter-en/perfcounter.md new file mode 100644 index 000000000..972269ff6 --- /dev/null +++ b/tutorials/katacoda/command-perfcounter-en/perfcounter.md @@ -0,0 +1,60 @@ + +Check the current JVM Perf Counter information. + +`perfcounter -h`{{execute T2}} + +```bash + USAGE: + perfcounter [-d] [-h] + + SUMMARY: + Display the perf counter infornation. + + Examples: + perfcounter + perfcounter -d + + WIKI: + https://alibaba.github.io/arthas/perfcounter + + OPTIONS: + -d, --details print all perf counter details + -h, --help this help +``` + +## Usage + +`perfcounter`{{execute T2}} + +```bash +$ perfcounter + java.ci.totalTime 2325637411 + java.cls.loadedClasses 3403 + java.cls.sharedLoadedClasses 0 + java.cls.sharedUnloadedClasses 0 + java.cls.unloadedClasses 0 + java.property.java.version 11.0.4 + java.property.java.vm.info mixed mode + java.property.java.vm.name OpenJDK 64-Bit Server VM + ``` + +Print more information with the `-d` option: + +`perfcounter -d`{{execute T2}} + +```bash +$ perfcounter -d + Name Variability Units Value +--------------------------------------------------------------------------------- + java.ci.totalTime Monotonic Ticks 3242526906 + java.cls.loadedClasses Monotonic Events 3404 + java.cls.sharedLoadedClasses Monotonic Events 0 + java.cls.sharedUnloadedClasses Monotonic Events 0 + java.cls.unloadedClasses Monotonic Events 0 +``` + +## PS: for JVM above JDK9 + +If the information is not printed, when the application starts, add the following parameters: + +`--add-opens java.base/jdk.internal.perf=ALL-UNNAMED --add-exports java.base/jdk.internal.perf=ALL-UNNAMED`