:Import trace data from SkyWalking

Limitations

• Only the gRPC protocol for SkyWalking V3 (release version 8.0.0 or later) is supported.

• Requires Logtail 1.0.33 or later for Linux, or Logtail 1.0.33.0 or later for Windows.

Step 1: Configure data import

1. Log on to the Simple Log Service console.

2. In the Import Data section, select SkyWalking.

3. Select the project that contains your trace instance and the ${instance}-traces Logstore.

4. Create a machine group.

   • If you have an available machine group, click Use Existing Machine Groups.

   • If you do not have an available machine group, follow these steps. This example uses an ECS instance.

     1. On the ECS Instances tab, manually select the target ECS instance and click Create.

        For more information, see Install Logtail on an ECS instance.

        Important

        If your server is an ECS instance that belongs to a different Alibaba Cloud account, a server from another cloud provider, or a server in a data center, you must manually install Logtail. Ensure that you install Logtail 1.0.33 or later for Linux, or 1.0.33.0 or later for Windows. 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 on the server. For more information, see Configure a user identifier.

     2. After you complete the installation, click Complete Installation.

     3. On the Create Machine Group page, enter a Name and click Next.

        Simple Log Service allows you to create machine groups based on IP addresses or custom user identifiers. For more information about the parameters, see Create an IP address-based machine group and Create a custom identifier-based machine group.

5. Confirm that the machine group is displayed in the Applied Server Groups section and 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 Simple Log Service. To resolve this issue, you can click Automatic Retry. If the issue persists, see What do I do if no heartbeat connections are detected on Logtail?

6. On the Specify Data Source tab, add the following configuration and click Next.

   Important

   Replace the ${instance} placeholder with the ID of your trace instance. To obtain the instance ID, see Create a trace instance.

   If port 11800 is in use on your Logtail server, 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 Logtail listener's address and port.

• If you use the Java Agent, replace the value of the collector.backend_service parameter. For more information, see Java Agent configuration.

• If you use the .NET Core Agent, run the dotnet skyapm config ${service}${endpoint} command to generate a configuration file. Replace ${service} with your actual service name and ${endpoint} with the IP address and port number of the machine group that you configured in Step 1: Configure data import. For more information, see SkyAPM-dotnet.

• If you use another agent or SDK to send data, replace the backend address with the IP address and port number of the machine group that you configured in Step 1: Configure data import.

Troubleshooting

If you do not see data on the preview or query page after configuring Logtail to collect trace data, see Troubleshoot Logtail log collection failures.