30 lines
1.1 KiB
Markdown
30 lines
1.1 KiB
Markdown
---
|
|
stage: Enablement
|
|
group: Distribution
|
|
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
|
|
type: reference
|
|
---
|
|
|
|
# Diagnostics tools **(FREE SELF)**
|
|
|
|
These are some of the diagnostics tools the GitLab Support team uses during troubleshooting.
|
|
They are listed here for transparency, and they may be useful for users with experience
|
|
with troubleshooting GitLab. If you are currently having an issue with GitLab, you
|
|
may want to check your [support options](https://about.gitlab.com/support/) first,
|
|
before attempting to use these tools.
|
|
|
|
## gitlabsos
|
|
|
|
The [gitlabsos](https://gitlab.com/gitlab-com/support/toolbox/gitlabsos/) utility
|
|
provides a unified method of gathering information and logs from GitLab and the system it's
|
|
running on.
|
|
|
|
## strace-parser
|
|
|
|
[strace-parser](https://gitlab.com/wchandler/strace-parser) is a small tool to analyze
|
|
and summarize raw `strace` data.
|
|
|
|
## Pritaly
|
|
|
|
[Pritaly](https://gitlab.com/wchandler/pritaly) takes Gitaly logs and colorizes output
|
|
or converts the logs to JSON.
|