72f07b812a
* Add Light4J 1.6.x plug-in * Add unit test for Light4J plug-in * Add missing id to server-starter * Remove mentions of version 1.6.x Some local testing showed that the plugin successfully generated traces for a light4j project built with light-codegen v2.x. Therefore, there is no need for a separate plugin for v2.x and no distinction needs to be made with light4j v1.6.x. * Update supported light4j versions * Use ContextSnapshot to maintain trace In a typical Light4j project, the ExceptionHandler#handleRequest is the asynchronous execution point. The flow is ExceptionHandler#handleRequest -> HttpServerExchange#dispatch -> ... -> ExceptionHandler#handleRequest. This means that handleRequest is being intercepted twice and each time a LocalSpan is created. Without handling thread propagation, the trace segment gets split up. By saving a ContextSnapshot into the enhanced object (ExceptionHandler), we can determine if it is necessary to continue the segment. * Update logic for span creation in trace By default, the Light4J plugin now overrides the Undertow plugin's entry span with its own. This new entry span is created just before execution of the ExceptionHandler#handleRequest in the I/O thread. The entry span is generated here because it is considered the starting point of the Light4J handler chain. There is now also the option to enable detailed span creation when tracing requests through Light4J. These local spans mark which middleware and business handlers are involved with handling the HTTP request to a Light4J service. * Update skywalking version * Update light4j version * Fix LightInstrumentation javadoc * Remove import violating checkstyle This import was added from the link reference in the javadoc. The javadoc has now been changed to just reference the method name. * Move light4j agent config property * Sync UI |
||
|---|---|---|
| .. | ||
| en | ||
| README.md | ||
| powered-by.md | ||
README.md
Welcome
Here are SkyWalking 6 official documents. Welcome to join us
From here you can learn all about SkyWalking’s architecture, how to deploy and use SkyWalking, also develop based on SkyWalking.
- Concepts and Designs. Concepts and designs explain the most important core ideas about SkyWalking. You can learn from here if you want to understand what is going on under our cool features and visualization.
- Setup. Setup contains guides for installing SkyWalking in different scenarios. As a platform, it provides several ways to provide observability, including monitoring and alarm of course.
- Contributing Guides. Guides are for PMC member, committer or new contributor. At here, you can know how to contribute from beginning.
- Protocols. Protocols show the communication ways between agents/probes and backend. Anyone, interested in uplink telemetry data, definitely should read this.
- FAQs. Include a manifest, including already known setup problems, secondary developments experiments. When you are facing a problem, check here first.
In addition, you might find these links interesting:
- The latest and old releases are all available at Apache SkyWalking release page. The change logs are here.
- You can find the speaking schedules at Conf, online videos and articles about SkyWalking in Community resource catalog. Also, if you have some related to us, welcome to submit a pull request to add.
- We’re always looking for help improving our documentation and codes, so please don’t hesitate to file an issue if you see some problem. Or better yet, submit your own contributions through pull request to help make them better.
Users from 5.x
SkyWalking 5.x is still supported by the community. For the user plans to upgrade from 5.x to 6.x, you should know there are some definitions of concepts changed.
The most important two changed concepts are
- Application(in 5.x) is changed to Service(in 6.x), also Application Instance is changed to Service Instance.
- Service(in 5.x) is changed to Endpoint(in 6.x).