platform
platform copied to clipboard
feat(dashmate): add `dashmate doctor` command
Issue being fixed or feature implemented
For investigation and bug reporting of the masternode services user should be able to get all possible logs in one place so that it could analyzed or handed to the support team.
This PR introduces an dashmate doctor command that will collect all possible information about dashmate node, and create an archive in the current working directory, where this command was issued from. It will grab and collect such info:
- General Operating System Info (arch, cpu, mem, swap)
- Docker container status and logs for each service (exit code, stdout, stderr)
- Core RPC info (best chain lock, quorums, blockchainInfo, peers, masternode status)
- Tenderdash RPC info (status, genesis, net_info, abci_info, dump_consesus_state)
- Tenderdash & Drive metrics (if they are enabled in the config)
What was done?
Implemented a new command that creates an archive with all gathered information for the user
How Has This Been Tested?
Locally
Breaking Changes
No
Checklist:
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have added or updated relevant unit/integration/functional/e2e tests
- [ ] I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
- [ ] I have made corresponding changes to the documentation if needed
For repository code-owners and collaborators only
- [ ] I have assigned this pull request to a milestone