From bff4e2a665db7ab30ded0bba967d30313df6880a Mon Sep 17 00:00:00 2001
From: Daniel Diniz <8012210-dnldnz@users.noreply.gitlab.com>
Date: Mon, 20 Nov 2023 19:48:27 +0000
Subject: [PATCH] Where to find geo.log in Kubernetes

---
 doc/administration/logs/index.md | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/doc/administration/logs/index.md b/doc/administration/logs/index.md
index b760f0b6217b7..b32d19f174fd7 100644
--- a/doc/administration/logs/index.md
+++ b/doc/administration/logs/index.md
@@ -985,8 +985,15 @@ For example:
 
 ## `geo.log` **(PREMIUM SELF)**
 
-Geo stores structured log messages in a `geo.log` file. For Linux package
-installations, this file is at `/var/log/gitlab/gitlab-rails/geo.log`.
+Geo stores structured log messages in a `geo.log` file. For Linux package installations,
+this file is at `/var/log/gitlab/gitlab-rails/geo.log`.
+
+For Helm chart installations, it's stored in the Sidekiq pod, at `/var/log/gitlab/geo.log`.
+It can be read by either directly accessing the file, or by using `kubectl` to fetch the Sidekiq logs, and subsequently filtering the results by `"subcomponent"=="geo"`. The example below uses `jq` to grab only Geo logs:
+
+```shell
+kubectl logs -l app=sidekiq --max-log-requests=50 | jq 'select(."subcomponent"=="geo")'
+```
 
 This file contains information about when Geo attempts to sync repositories
 and files. Each line in the file contains a separate JSON entry that can be
-- 
GitLab