Closed obycode closed 1 month ago
Most of the useful information is directly in a single log, but some of it would need to be accumulated (e.g. identifying the block that a block-commit is confirming).
Somehow adding timestamps would be very helpful, both to understand the timing between events, and to map back into the logs.
I have completed the setup of the tool, making it dev-friendly by updating its naming conventions, code structure, and documentation in the README. I believe this issue can be closed. If any specific needs arise in the future, I can make the necessary changes to the tool. Additionally, the steps to follow are straightforward, so others can easily make modifications as needed.
The tool can be found here https://github.com/hirosystems/log-analysis-tool. If there is anything else needed to finish the tool setup, please let me know.
Thanks @ASuciuX.
From various times debugging issues in our naka-1 testnet, I've found that it could be useful to have a tool to help me comb through the logs to figure out what is going on. This tool would take in a log file (text) and generate a sequence diagram showing the various activities of Bitcoin, the Stacks miner, and the signers. For starters, something like this could be helpful: