mirror of
https://gitee.com/arthas/arthas.git
synced 2024-12-12 12:05:13 +08:00
40 lines
2.8 KiB
Markdown
40 lines
2.8 KiB
Markdown
|
||
|
||
|
||
|
||
|
||
`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 threads, 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 threads.
|
||
|
||
## 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, thread 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 simple application as an example to demonstrate the use case of Find CPU usage Top N threads.
|
||
|
||
* Github: https://github.com/alibaba/arthas
|
||
* Docs: https://arthas.aliyun.com/doc/en
|