[GitHub] [pulsar] ni-ze opened a new issue #7323: How Pulsar functions supported the aggregation when deal with the tracing data?

[GitBox <gi...@apache.org>]

ni-ze opened a new issue #7323:
URL: https://github.com/apache/pulsar/issues/7323


   Those are my data:
   
   ```
   {"traceId":"912677f3-bbdc-46b9-83e8-28b9dc53b62a","parentId":"912677f3-bbdc-46b9-83e8-28b9dc53b62a","id":"0977e19c-3581-484f-9426-fd9391c64534","kind":"CLIENT","name":"http:/echo/auto-test-1","timestamp":1591151294760000,"duration":5000,"localEndpoint":{"serviceName":"consumer-demo","ipv4":"10.64.35.49","port":18083},"remoteEndpoint":{"serviceName":"provider-demo","ipv4":"10.64.35.49","port":18081},"annotations":[{"timestamp":1591151294765000,"value":"{\"name\":\"test\",\"value\":\"123\"}"}],"tags":{"custom.test":"123","http.host":"10.64.35.49","http.method":"GET","http.path":"/echo/auto-test-1","http.url":"http://10.64.35.49:18081/echo/auto-test-1","localInterface":"doWork","remoteInterface":"/echo/auto-test-1","resultStatus":"200","spring.instance_id":"10.64.35.49:consumer-demo:18083"}}
   {"traceId":"912677f3-bbdc-46b9-83e8-28b9dc53b62a","id":"912677f3-bbdc-46b9-83e8-28b9dc53b62a","kind":"SERVER","name":"do-work","timestamp":1591151294757000,"duration":8891,"localEndpoint":{"serviceName":"consumer-demo","ipv4":"10.64.35.49","port":18083},"annotations":[{"timestamp":1591151294766000,"value":"{\"name\":\"test\",\"value\":\"123\"}"}],"tags":{"class":"ScheduledProviderDemo","custom.test":"123","localInterface":"doWork","method":"doWork","resultStatus":"200","spring.instance_id":"10.64.35.49:consumer-demo:18083"}}
   ```
   
   I want to find them out from stream use pulsar functions, which means I must find out the message with same traceId. so, here is question, how to realize use pulsar functions?
   
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org