summaryrefslogtreecommitdiff
path: root/doc/administration/gitaly
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-03-09 00:08:14 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2020-03-09 00:08:14 +0000
commited4df05ce917d6cf175aeb508b0485ae5f281a0a (patch)
tree9313abd8fd41a78eb2bf1ffd0f95f10b69cd25cb /doc/administration/gitaly
parent1bdb3fe3821fc3d222361d8b2e2ec2fea2915372 (diff)
downloadgitlab-ce-ed4df05ce917d6cf175aeb508b0485ae5f281a0a.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/gitaly')
-rw-r--r--doc/administration/gitaly/reference.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/administration/gitaly/reference.md b/doc/administration/gitaly/reference.md
index 2c5e54743c3..6b6919247fe 100644
--- a/doc/administration/gitaly/reference.md
+++ b/doc/administration/gitaly/reference.md
@@ -233,7 +233,7 @@ The following values configure logging in Gitaly under the `[logging]` section.
| `sentry_environment` | string | no | [Sentry Environment](https://docs.sentry.io/enriching-error-data/environments/) for exception monitoring. |
| `ruby_sentry_dsn` | string | no | Sentry DSN for `gitaly-ruby` exception monitoring. |
-While the main Gitaly application logs go to stdout, there are some extra log
+While the main Gitaly application logs go to `stdout`, there are some extra log
files that go to a configured directory, like the GitLab Shell logs.
GitLab Shell does not support `panic` or `trace` level logs. `panic` will fall
back to `error`, while `trace` will fall back to `debug`. Any other invalid log