Log Service:Import trace data from SkyWalking

Limits

Only the GRPC protocol of SkyWalking V3 is supported. The release version of SkyWalking is 8.0.0 or later.

Step 1: Configure data import

1. Log on to the Log Service console.
2. In the Import Data section, select SkyWalking.
3. Select the project and the ${instance}-traces Logstore where your trace instance resides.
4. Create a machine group.
   • If a machine group is available, click Use Existing Machine Groups.
   • If no machine groups are available, perform the following steps to create a machine group. In this example, an Elastic Compute Service (ECS) instance is used.
     1. On the ECS Instances tab, select Manually Select Instances. Then, select the ECS instance that you want to use and click Create.

        For more information, see Install Logtail on ECS instances.

        Important If you want to collect logs from an ECS instance that belongs to a different Alibaba Cloud account, a server in an on-premises data center, or a server of a third-party cloud service provider, you must manually install Logtail. For more information, see Install Logtail on a Linux server or Install Logtail on a Windows server.

        After you manually install Logtail, you must configure a user identifier for the server. For more information, see Configure a user identifier.

     2. After Logtail is installed, click Complete Installation.
     3. In the Create Machine Group step, configure the Name parameter and click Next.

        Log Service allows you to create IP address-based machine groups and custom identifier-based machine groups. For more information, see Create an IP address-based machine group and Create a custom identifier-based machine group.

5. Select the new machine group from the Source Server Groups section and move the machine group to the Applied Server Groups section. Then, click Next.
   Important If you apply a machine group immediately after you create the machine group, the heartbeat status of the machine group may be FAIL. This issue occurs because the machine group is not connected to Log Service. To resolve this issue, you can click Automatic Retry. If the issue persists, see What do I do if a Logtail machine group has no heartbeats?
6. In the Specify Data Source step, add the following configurations and click Next.
   Important ${instance} indicates the ID of your trace instance. Replace the variable with an actual ID. For information about how to obtain the ID of a trace instance, see Create a trace instance.

   If your Logtail local port 11800 is occupied, you can replace it with another available port.

   {
       "inputs" : [
           {
               "detail" : {
                   "Address" : "0.0.0.0:11800"
               },
               "type" : "service_skywalking_agent_v3"
           }
       ],
       "aggregators" : [
           {
               "detail" : {
                   "MetricsLogstore" : "${instance}-metrics",
                   "TraceLogstore" : "${instance}-traces"
               },
               "type" : "aggregator_skywalking"
           }
       ],
       "global" : {
           "AlwaysOnline" : true,
           "DelayStopSec" : 300
       }
   }

Step 2: Configure the SkyWalking client

Configure the SkyWalking client to send data to the address of the Logtail listener. Take note of the following items:

• If you are using Java Agent, replace the value of the collector.backend_service parameter. For more information, see Java Agent configuration.
• If you are using .net core Agent, use the dotnet skyapm config ${service}${endpoint} command to generate the configuration file. In this case, you must replace the ${service} variable with an actual service name. You must replace the ${endpoint} variable with the machine group IP address and the port number that are configured in Step 5. For more information, see SkyAPM-donet.
• If you are using another agent or SDK to send data, replace the backend address with the machine group IP address and the port number that are configured in Step 5.