-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
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
Design for Tx level tracing and Analysis mode #215
Labels
pinned
Pin this issue to prevent from auto-closing
Comments
this looks like distributed tracing. why should this be handled by |
This was
linked to
pull requests
Nov 7, 2021
|
|
adding some log samples |
I suppose as so far with jaeger span, we are able to make tx level tracing and analysis by jaeger. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your proposal related to a problem?
(Write your answer here.)
Describe the solution you'd like
When:
Tape sending Tx to Fabric network, we hope to have tracing key timestamps as
then:
We do analysis basing on records above and output with analysis report as csv file below:
tx | tape start time | peer1 endorsement time | peer2 endorsement time | ... | peer n endorsement time | envelop time | block no | orderer blocking time | peer1 commit time | peer2 commit time | ... | peer n commit time |
(Describe your proposed solution here.)
Describe alternatives you've considered
with consider above, I would like to save recording into files and analysis after tape completed. and this recording file saved for further usage.
see have some internal structure to save the data in memory.
once some worker(as traffics generator complete with one tx generate, this tx will be send to a channel and save in memory before it saved into file.)
where will be some go-routine there with low level priority reading from channel and save data into file.
as
tx | time | event name
txID | Oct-22 | generated
txID | Oct-22 | peer1 endorsement
...
the analysis mode will reading data from files and do analysis and generated with final report into csv.
(Write your answer here.)
Additional context
(Write your answer here.)
The text was updated successfully, but these errors were encountered: