Skip to content
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

feat(dashmate): add dashmate doctor command #2024

Merged
merged 27 commits into from
Aug 23, 2024
Merged

Conversation

pshenmic
Copy link
Collaborator

@pshenmic pshenmic commented Jul 30, 2024

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

@pshenmic pshenmic self-assigned this Jul 30, 2024
@pshenmic pshenmic marked this pull request as draft July 30, 2024 11:16
packages/dashmate/src/commands/doctor.js Outdated Show resolved Hide resolved
packages/dashmate/src/commands/doctor.js Outdated Show resolved Hide resolved
packages/dashmate/src/commands/doctor.js Outdated Show resolved Hide resolved
packages/dashmate/src/doctor/report.js Outdated Show resolved Hide resolved
packages/dashmate/src/doctor/report.js Outdated Show resolved Hide resolved
packages/dashmate/src/commands/doctor.js Outdated Show resolved Hide resolved
packages/dashmate/src/commands/doctor.js Outdated Show resolved Hide resolved
packages/dashmate/src/commands/doctor.js Outdated Show resolved Hide resolved
packages/dashmate/src/commands/doctor.js Outdated Show resolved Hide resolved
packages/dashmate/src/commands/doctor.js Outdated Show resolved Hide resolved
Copy link
Member

@shumkov shumkov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yarn cache is not committed

packages/dashmate/src/commands/doctor.js Outdated Show resolved Hide resolved
@pshenmic pshenmic marked this pull request as ready for review August 22, 2024 11:07
@shumkov shumkov merged commit c3fd93c into v1.0-dev Aug 23, 2024
21 checks passed
@shumkov shumkov deleted the feat/dashmate-report branch August 23, 2024 06:33
@shumkov shumkov added this to the v1.1.0 milestone Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants