Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
c7c7ece6
Commit
c7c7ece6
authored
Apr 19, 2021
by
Will Chandler
Committed by
Evan Read
Apr 19, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add note on enabling gRPC tracing in Gitaly
parent
dea506b0
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
15 additions
and
0 deletions
+15
-0
doc/administration/gitaly/index.md
doc/administration/gitaly/index.md
+15
-0
No files found.
doc/administration/gitaly/index.md
View file @
c7c7ece6
...
...
@@ -459,6 +459,21 @@ You can run a gRPC trace with:
sudo
GRPC_TRACE
=
all
GRPC_VERBOSITY
=
DEBUG gitlab-rake gitlab:gitaly:check
```
### Server side gRPC logs
gRPC tracing can also be enabled in Gitaly itself with the
`GODEBUG=http2debug`
environment variable. To set this in an Omnibus GitLab install:
1.
Add the following to your
`gitlab.rb`
file:
```
ruby
gitaly
[
'env'
]
=
{
"GODEBUG=http2debug"
=>
"2"
}
```
1.
[
Reconfigure
](
../restart_gitlab.md#omnibus-gitlab-reconfigure
)
GitLab.
### Correlating Git processes with RPCs
Sometimes you need to find out which Gitaly RPC created a particular Git process.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment