Skip to content

Documentation for mz-debug #32099

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

Merged
merged 6 commits into from
Apr 21, 2025
Merged

Documentation for mz-debug #32099

merged 6 commits into from
Apr 21, 2025

Conversation

SangJunBak
Copy link
Contributor

@SangJunBak SangJunBak commented Apr 4, 2025

Still working on actually deploying the binaries but the docs should stay relatively the same.

Will make a followup PR to make changes to the self managed docs branch.

Motivation

Tips for reviewer

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

@SangJunBak SangJunBak requested a review from kay-kim April 4, 2025 20:39
@SangJunBak SangJunBak requested a review from a team as a code owner April 4, 2025 20:39
@@ -106,6 +106,23 @@ not suitable for full feature set evaluations or production workloads.
For questions, discussions, or general technical support, join the [Materialize
Community on Slack](https://materialize.com/s/chat).

#### `mz-debug`
Copy link
Contributor

@kay-kim kay-kim Apr 7, 2025

Choose a reason for hiding this comment

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

As an fyi -- we'll need to manually add teh mz-debug page to https://github.com/MaterializeInc/materialize/blob/main/doc/user/content/integrations/_index.md page as well.

@SangJunBak SangJunBak changed the title Separate emulator and self-managed sub-commands Documentation for mz-debug Apr 7, 2025
@kay-kim kay-kim marked this pull request as draft April 8, 2025 18:09
kay-kim and others added 3 commits April 9, 2025 13:16
- We can actually specify the global options anywhere. I still wanted to separate the global flags from the non-global flags however. Thus I put it in the bottom, similar to Cockroach
- Changed the install instructions for linux. Also tested in a linux VM as well.
@SangJunBak SangJunBak marked this pull request as ready for review April 21, 2025 16:02
@SangJunBak SangJunBak requested a review from kay-kim April 21, 2025 16:03
@SangJunBak
Copy link
Contributor Author

@kay-kim made some changes in the last commit! Sorry this took so long!


## Installation

```shell
Copy link
Contributor

Choose a reason for hiding this comment

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

We should separate these so that the commands are actually copyable.
We can use tabs or use separate subheaders.

disable_list: true
---

`mz-debug` is a command-line interface tool that collects debug information for self-managed and emulator Materialize environments. By default, the tool creates a compressed file (`.zip`) containing logs and a dump of the system catalog. You can then share this file with support teams when investigating issues.
Copy link
Contributor

Choose a reason for hiding this comment

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

Q: Is the "By default" referring to that contents; i.e., the logs and the dump of the system catalog? as opposed to you can have it not create the zip file and do something instead?

@@ -106,6 +106,23 @@ not suitable for full feature set evaluations or production workloads.
For questions, discussions, or general technical support, join the [Materialize
Community on Slack](https://materialize.com/s/chat).

#### `mz-debug`

Materialize provides a command-line debug tool called `mz-debug` that helps collect diagnostic information from your emulator environment. This tool can gather:
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe:

Materialize provides mz-debug, a command-line debug tool, that collects diagnostic information from your emulator environment. This tool can gather:

@SangJunBak SangJunBak merged commit ad99773 into main Apr 21, 2025
11 checks passed
@SangJunBak SangJunBak deleted the jun/#8908/polish branch April 21, 2025 16:23
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