shelltea commented on issue #8305:
URL: https://github.com/apache/skywalking/issues/8305#issuecomment-995688011


   I think I found the problem.
   The segment in elasticsearch:
   ```
   {
        "_index": "sw_segment-20211216",
        "_type": "_doc",
        "_id": "0ce24b8c082e4f1bb38e4fc472889645.175.16396487055200000",
        "_version": 1,
        "_seq_no": 4525794,
        "_primary_term": 1,
        "found": true,
        "_source": {
                "start_time": 1639648705520,
                "trace_id": 
"0ce24b8c082e4f1bb38e4fc472889645.175.16396487055200001",
                "data_binary": "",
                "service_id": "a3MtdHJhY2UtaWQtd2Vi.1",
                "latency": 270,
                "time_bucket": 20211216175825,
                "endpoint_id": "a3MtdHJhY2UtaWQtd2Vi.1_R0VUOi9h",
                "is_error": 0,
                "service_instance_id": 
"a3MtdHJhY2UtaWQtd2Vi.1_a3MtdHJhY2UtaWQtd2ViLWxvY2Fs",
                "segment_id": 
"0ce24b8c082e4f1bb38e4fc472889645.175.16396487055200000",
                "tags": [
                        "http.method=GET",
                        
"http.headers=x-request-id=[256ce597-1e0e-4086-a78a-deaf9ead8b45]\nx-correlation-id=[579b8397-17a4-4cf3-a4d5-477106f8f613]"
                ]
        }
   }
   ``` 
   There is a `\n` between the two headers. When I search on trace page the 
condition is:
   ```
   [
     {
       "key": "http.headers",
       "value": "x-request-id=[256ce597-1e0e-4086-a78a-deaf9ead8b45] 
x-correlation-id=[579b8397-17a4-4cf3-a4d5-477106f8f613]"
     }
   ]
   ```
   So I changed the config to`SW_PLUGIN_HTTP_INCLUDE_HTTP_HEADERS=x-request-id` 
only include one header, And now I can search like this:
   
![image](https://user-images.githubusercontent.com/864375/146360430-accd128e-5a84-42c5-9d65-7f0c293eaa5c.png)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to