fixed maven 3.3.9 build issue caused by empty assembly ID on Ubuntu 16.04.2 using OpenJDK 1.8.0_151. [INFO] Building apm-collector-boot 5.0.0-alpha [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ apm-collector-boot --- [INFO] Deleting /home/steve/skywalking/incubator-skywalking/apm-collector/apm-collector-boot/target [INFO] [INFO] --- maven-checkstyle-plugin:2.17:check (validate) @ apm-collector-boot --- [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1.492 s [INFO] Finished at: 2018-02-18T12:05:49-06:00 [INFO] Final Memory: 19M/235M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:2.17:check (validate) on project apm-collector-boot: Failed during checkstyle configuration: cannot initialize module Header - Unable to find: CHECKSTYLE_HEAD -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException |
||
|---|---|---|
| .github | ||
| apm-application-toolkit | ||
| apm-collector | ||
| apm-commons | ||
| apm-protocol | ||
| apm-sniffer | ||
| ci-dependencies | ||
| docs | ||
| .gitignore | ||
| .travis.yml | ||
| CHECKSTYLE_HEAD | ||
| CODE_OF_CONDUCT.md | ||
| DISCLAIMER | ||
| HEADER | ||
| LICENSE | ||
| NOTICE.txt | ||
| README.md | ||
| README_ZH.md | ||
| checkStyle.xml | ||
| codeStyle.xml | ||
| docker-compose.yml | ||
| pom.xml | ||
README.md
Apache SkyWalking | 中文
SkyWalking: APM (application performance monitor) tool for distributed systems, especially designed for microservices, cloud native and container-based (Docker, K8s, Mesos) architectures. Underlying technology is a distributed tracing system.
- Provide Java agent, no need to CHANGE any application source code.
- High performance agent. Only increase extra 10% cpu cost in 5000+ tps application, even when collect all traces.
- Supported middlewares, frameworks and libraries.
- Manual instrumentation
- As an OpenTracing supported tracer
- Use @Trace annotation for any methods you want to trace.
- Integrate traceId into logs for log4j, log4j2 and logback.
- Pure Java server implementation, provide RESTful and gRPC services. Compatibility with other language agents/SDKs.
- The UI released on skywalking-ui
Document
5.x Architecture
Code of conduct
This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to wusheng@apache.org.
Screenshots
-
Discovery topological graph of application clusters automatically.

-
Trace query.

-
Span detail.

-
Instance Overview.

-
JVM Detail.

-
Services Dependency Tree.

Test reports
- Automatic integration test reports
- Performance test reports
Contact Us
- Submit an issue
- Gitter
- QQ Group: 392443393