@@ -3,7 +3,7 @@ This document describe how to understand, develop and contribute plugin.
There are 2 kinds of plugin
1.[Tracing plugin](#tracing-plugin). Follow the distributed tracing concept to collect spans with tags and logs.
1.[Meter plugin](#meter-plugin). Collect numeric metrics in Counter, Guage, and Histogram formats.
1.[Meter plugin](#meter-plugin). Collect numeric metrics in Counter, Gauge, and Histogram formats.
We also provide the [plugin test tool](#plugin-test-tool) to verify the data collected and reported by the plugin. If you plan to contribute any plugin to our main repo, the data would be verified by this tool too.
@@ -150,7 +150,7 @@ miss any newly-added dependency:
## Profile
The performance profile is an enhancement feature in the APM system. We are using the thread dump to estimate the method execution time, rather than adding many local spans. In this way, the resource cost would be much less than using distributed tracing to locate slow method. This feature is suitable in the production environment. The following documents are important for developers to understand the key parts of this feature
-[Profile data report procotol](https://github.com/apache/skywalking-data-collect-protocol/tree/master/profile) is provided like other trace, JVM data through gRPC.
-[Profile data report protocol](https://github.com/apache/skywalking-data-collect-protocol/tree/master/profile) is provided like other trace, JVM data through gRPC.
-[Thread dump merging mechanism](backend-profile.md) introduces the merging mechanism, which helps the end users to understand the profile report.
-[Exporter tool of profile raw data](backend-profile-export.md) introduces when the visualization doesn't work well through the official UI, how to package the original profile data, which helps the users report the issue.