We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello and thank you for this awesome work!
I was working on changing the code to use jsonencode instead of prettyjson, when i stumbled across an odd behavior, described as example below.
jsonencode
prettyjson
Perhaps I have a different understanding on how to interpret the trace data, in which case I am also happy to be corrected.
For the creation of parallel traces. The behaviour is the same for sequential traces.
For the traceid=0b0ab4e315919238654535000ead8e:
traceid=0b0ab4e315919238654535000ead8e
basic structure as 'graph'
"" |_ 7695b43b41732a0f15d3799c8eed2852665fe8da29fd700c383550fc16e521a3 -> s0 |_ 9a3ef4d24dd4e7fb8baaa9e30aea1395caa50f583630f69047c8e20f2e8d9554 -> s1 |_ [calls self] -> skipped |_ 9653f5baba69c9fb50bfb30a8571eb04dbceaae7c7f379e20bd73a41168a2913 -> s2 |_ 9ee59483550ea795bc04e930ad6b37b7852e92fa9a71556565e91380dd39de03 -> s3
in words:
so I believe the resulting trace should look something like this:
{ "s0": [ {"s1": [ {"s2": [{}]}, {"s3": [{}]} ]} ] }
{ "s0":[ {"s2":[{}]}, {"s1":[ {"s3":[{}]} ]} ] }
Nr = [50584; 50581; 50580; 50579; 50583]; traceid = ["0b0ab4e315919238654535000ead8e";"0b0ab4e315919238654535000ead8e";"0b0ab4e315919238654535000ead8e";"0b0ab4e315919238654535000ead8e";"0b0ab4e315919238654535000ead8e"]; timestamp = [265451; 265457; 265457; 265460; 265460]; rpcid = ["0"; "0.1"; "0.1.1"; "0.1.2"; "0.1.2.1"]; um = [""; ... "7695b43b41732a0f15d3799c8eed2852665fe8da29fd700c383550fc16e521a3"; ... "9a3ef4d24dd4e7fb8baaa9e30aea1395caa50f583630f69047c8e20f2e8d9554"; ... "9a3ef4d24dd4e7fb8baaa9e30aea1395caa50f583630f69047c8e20f2e8d9554"; ... "9a3ef4d24dd4e7fb8baaa9e30aea1395caa50f583630f69047c8e20f2e8d9554"]; rpc_type = ["http"; "http"; "mc"; "rpc";"mc"]; dm = ["7695b43b41732a0f15d3799c8eed2852665fe8da29fd700c383550fc16e521a3"; ... "9a3ef4d24dd4e7fb8baaa9e30aea1395caa50f583630f69047c8e20f2e8d9554"; ... "9653f5baba69c9fb50bfb30a8571eb04dbceaae7c7f379e20bd73a41168a2913"; ... "9a3ef4d24dd4e7fb8baaa9e30aea1395caa50f583630f69047c8e20f2e8d9554"; ... "9ee59483550ea795bc04e930ad6b37b7852e92fa9a71556565e91380dd39de03"]; interface = ["1f888de4377607e9402377e6ab0e83cc3c542b95e9c2133caa7e29e2028796a0"; ... "1f888de4377607e9402377e6ab0e83cc3c542b95e9c2133caa7e29e2028796a0"; ... ""; ... "da36ccfdc24fd53f0626f1a2b234ded133e139f240ae650cd6f707c424c5c3e8"; ... ""]; response_time = [-8; -4; 1; 0; 0]; trace = table(Nr, traceid, timestamp, rpcid, um, rpc_type, dm, interface, response_time); % skipping service_graphs... names_map = unique([trace.um ; trace.dm]); concatted = get_json_mubench('0.1',trace,names_map,0) jsonencode(jsondecode("{"+concatted+"}"), "PrettyPrint",true)
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Hello and thank you for this awesome work!
I was working on changing the code to use
jsonencode
instead ofprettyjson
, when i stumbled across an odd behavior, described as example below.Perhaps I have a different understanding on how to interpret the trace data, in which case I am also happy to be corrected.
Example
For the creation of parallel traces. The behaviour is the same for sequential traces.
Input data
For the
traceid=0b0ab4e315919238654535000ead8e
:basic structure as 'graph'
in words:
so I believe the resulting trace should look something like this:
Expected Results
Actual Results
Comparison
Matlab Code
The text was updated successfully, but these errors were encountered: