Open oberstet opened 7 years ago
There is a glitch with the last
flag an WAMP meta events. Eg consider the following block from here https://gist.githubusercontent.com/oberstet/4071ae81cdd8d46c6367eb3c272304d2/raw/f732ab681848b8c860fb62931386882a24ebefb8/gistfile1.txt
cf1 worker-001 trace2 RX Subscribe 3189696406725083 True False c668c5d6-e978-45d8-b972-3ecda3e87330 com.example.r1948
cf1 worker-001 trace2 TX Subscribed 3189696406725083 False False c668c5d6-e978-45d8-b972-3ecda3e87330 com.example.r1948
cf1 worker-001 trace2 RX Publish 8801905038089636 False False c668c5d6-e978-45d8-b972-3ecda3e87330 wamp.subscription.on_create
cf1 worker-001 trace2 TX Event 4320835592887046 False False c668c5d6-e978-45d8-b972-3ecda3e87330 wamp.subscription.on_create
cf1 worker-001 trace2 TX Event 316910278652384 False True c668c5d6-e978-45d8-b972-3ecda3e87330 wamp.subscription.on_create
cf1 worker-001 trace2 RX Publish 8801905038089636 False True c668c5d6-e978-45d8-b972-3ecda3e87330 wamp.subscription.on_subscribe
cf1 worker-001 trace2 TX Event 4320835592887046 False False c668c5d6-e978-45d8-b972-3ecda3e87330 wamp.subscription.on_subscribe
cf1 worker-001 trace2 TX Event 316910278652384 False True c668c5d6-e978-45d8-b972-3ecda3e87330 wamp.subscription.on_subscribe
here is another run: https://gist.githubusercontent.com/oberstet/3128a416e2e733b383c26e4be975b031/raw/9182172d05ea3d10a1002a297721f020f9511f2e/gistfile1.txt
the setup was: 1x CF, 2x WAMP meta API monitor comp., 2x App component
good thing is, the new correlation_is_last
flag is now correct at the app call/publication level:
Node Worker Trace Dir Type Session Anchor Last Correlation ID Correlation URI
................................................................................................................................................................
cf1 worker-001 trace2 RX Call 6725202028798054 True False c7f8025f-6247-41be-844c-f19c603994fe com.example.add2
cf1 worker-001 trace2 TX Invocation 1082396409294685 False False c7f8025f-6247-41be-844c-f19c603994fe com.example.add2
cf1 worker-001 trace2 RX Yield 1082396409294685 False False c7f8025f-6247-41be-844c-f19c603994fe com.example.add2
cf1 worker-001 trace2 TX Result 6725202028798054 False True c7f8025f-6247-41be-844c-f19c603994fe com.example.add2
Node Worker Trace Dir Type Session Anchor Last Correlation ID Correlation URI
................................................................................................................................................................
cf1 worker-001 trace2 RX Publish 6725202028798054 True False 253ff224-6a4e-48c2-8bff-51ae96737d3c com.example.oncounter
cf1 worker-001 trace2 TX Published 6725202028798054 False False 253ff224-6a4e-48c2-8bff-51ae96737d3c com.example.oncounter
cf1 worker-001 trace2 TX Event 2489530629840806 False False 253ff224-6a4e-48c2-8bff-51ae96737d3c com.example.oncounter
cf1 worker-001 trace2 TX Event 1082396409294685 False False 253ff224-6a4e-48c2-8bff-51ae96737d3c com.example.oncounter
cf1 worker-001 trace2 TX Event 6725202028798054 False False 253ff224-6a4e-48c2-8bff-51ae96737d3c com.example.oncounter
cf1 worker-001 trace2 TX Event 7498650488609742 False True 253ff224-6a4e-48c2-8bff-51ae96737d3c com.example.oncounter
here is an extensive trace example I get with the current code: https://gist.githubusercontent.com/oberstet/050ce8c9b8b96e01e108a151ebb59f6c/raw/c1848b36de2307d5321bac36b0fdf39c5c10a1bb/gistfile1.txt
this is running 2 CF nodes with multiple app component clients and WAMP meta API clients