Tracing is not displayed or stored well

assimbly / runtime

Java & REST API's for creating and running integrations

Apache License 2.0

17 stars 3 forks source link

Tracing is not displayed or stored well #213

Closed Hooghof closed 3 months ago

Hooghof commented 4 months ago

There are 3 variants:

The order of the exchanges is wrong
The only displayed component is the Inbound HTTP component (Instance: next, Tenant: Regression Tests, Flow: Velocity, Postman Test: Velocity headers)
There is no tracing at all (for example in case of the Base64 component option unmarshall), no distinction in transport type

Hooghof commented 4 months ago

Test findings:

Most of the times, but not always, the individual exchanges are visible in the transactions now, except base64 marshall for example. Looks like it happens in case of transport type queues
The order of exchanges is not always chronological
The list of exchanges is getting longer after some tests

skin27 commented 3 months ago

Sometimes the tracing is not always in the right order. Norman didn't find a pattern yet, but will look into to get a reproducible thing.

We also need an integration test for testing tracing (for example by comparing the elastic query)

Hooghof commented 3 months ago

It's not exactly reproducible how this hapens, but the order of exchanges differs per call. You can test in the flow Tracing01 on next (tenant Microscope), by sending a message body to this url: https://next.dovetail.world/test/inbound_http/533057/Tracing01

Hooghof commented 3 months ago

The order of the transactions' exchanges looks fine now. What misses is the message body in every individual exchange. Only the last message body is shown.