This topic describes how to import trace data from Apache SkyWalking to Log Service. This way, you can query and analyze the trace data by using Log Service.
Prerequisites
- Apache SkyWalking
- A SkyWalking agent of version 8.0.0 or later is installed in the application on which data is collected. For more information, see Setup.
- Log Service
- A Logstore is created. For more information, see Create a Logstore.
- A machine group is created, and the group uses a custom identifier. For more information,
see Create a custom ID-based machine group.
Notice Make sure that the custom identifier is unique in the region of the Log Service project to which the Logstore belongs.
- A trace instance is created. For more information, see Create a trace instance.
Background information
We recommend that you import trace data from Apache SkyWalking to Log Service. This brings the following benefits:
- Elasticity: Log Service can handle traffic spikes in an efficient manner.
- Performance: Log Service provides higher query performance than open source Elasticsearch. Log Service allows you to write petabytes of data per day, and returns results to queries for billions or tens of billions of data rows within seconds.
- Stability: Log Service uses three replicas for storage, which provides 99.9% availability and 99.999999999% (eleven 9's) reliability.
- O&M: Log Service provides an out-of-the-box feature that allows you to import Apache SkyWalking trace data. O&M is not required for Log Service. You do not need to perform O&M on servers or applications.
Procedure
The following procedure describes how to import trace data from Apache SkyWalking to Log Service: