gabriel-farache commented on PR #4094:
URL: 
https://github.com/apache/incubator-kie-kogito-runtimes/pull/4094#issuecomment-3678705373

   > @wmedvede Currently, with what I pushed, using 
https://github.com/gabriel-farache/test-sonataflow-opentelemetry/blob/main/src/main/resources/yamlgreet.sw.yml
 this is the traces I get 
[trace.json](https://github.com/user-attachments/files/24272157/trace.json) 
<img alt="image" width="1917" height="420" 
src="https://private-user-images.githubusercontent.com/3036508/528878895-52a5c775-2f2f-4608-979c-78d5bc629938.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjYzMTYzNzQsIm5iZiI6MTc2NjMxNjA3NCwicGF0aCI6Ii8zMDM2NTA4LzUyODg3ODg5NS01MmE1Yzc3NS0yZjJmLTQ2MDgtOTc5Yy03OGQ1YmM2Mjk5MzgucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MTIyMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTEyMjFUMTEyMTE0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YTQ4YTAzMWM4M2VjNzk1ZmY0ODA2YzA4MzI3YTdjNWE1NmIwZjAxNDM1ZGEyZTVlYzIyYWNmNjFi
 
NDNkZjBjOSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.22Cb83hPAKaFQUPCeWQfM-ovTxdN1Ig76O3zr3gG7Fk">
   > 
   > This looks fine except for the span 
`sonataflow.process.anothergreetSubflow.execute` being a child of 
`GreetInEnglish` instead of `ExecuteSubflow` span.
   > 
   > Do we want to "force" a new trace creation for `ExecuteSubflow` after the 
sleep and for `waitForEvent`? For any suspension actually
   
   FYI the last commit solved the issue with the span hierarchy 


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to