gitlab-ce/doc/administration/troubleshooting/diagnostics_tools.md

stage	group	info	title
GitLab Delivery	Self Managed	To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments	Diagnostics tools

{{< details >}}

• Tier: Free, Premium, Ultimate
• Offering: GitLab Self-Managed

{{< /details >}}

These are some of the diagnostics tools the GitLab Support team uses during troubleshooting. They are listed here for transparency, and for users with experience with troubleshooting GitLab. If you are currently having an issue with GitLab, you may want to check your support options first, before attempting to use these tools.

SOS scripts

• gitlabsos gathers information and recent logs from a Linux package or Docker-based GitLab instance and its operating system.
• kubesos gathers k8s cluster configuration and recent logs from a GitLab Helm chart deployment.
• gitlab:db:sos gathers detailed diagnostic data about your database.

strace-parser

strace-parser analyzes and summarize raw strace data. The strace zine is recommended for context.

gitlabrb_sanitizer

1 outputs a copy of /etc/gitlab/gitlab.rb content with sensitive values redacted.

fast-stats

fast-stats summarizes errors and resource-intensive usage statistics quickly, to help debug performance and configuration problems. fast-stats is particularly useful to parse and compare large volumes of logs, or to start troubleshooting unknown problems.

greenhat

greenhat provides an interactive shell to analyze, filter, and summarize SOS logs.

GitLab Detective

GitLab Detective runs automated checks on a GitLab installation to identify and resolve common issues.