From dcb8bb9533916e5cd56cf87ba2edffcf31a092ea Mon Sep 17 00:00:00 2001
From: Gemma <58080601+gememma@users.noreply.github.com>
Date: Tue, 4 Feb 2025 15:41:47 +0000
Subject: [PATCH] Add instructions to CONTRIBUTING for changing the agent log
 level (#3062)

* Add instructions to CONTRIBUTING for changing the agent log level

* Changelog
---
 CONTRIBUTING.md                                       | 8 ++++++++
 changelog.d/+agent-log-level-instructions.internal.md | 1 +
 2 files changed, 9 insertions(+)
 create mode 100644 changelog.d/+agent-log-level-instructions.internal.md

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 8d9d7fdb3f4..d2f9b46952f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -465,6 +465,14 @@ To debug it with a debugger:
 
 ## Retrieving Agent Logs
 
+You can change the minimum severity of logs emitted by the agent by setting `agent.log_level` in the mirrord config
+file, for example:
+```json
+"agent": {
+	"log_level": "mirrord=trace"
+}
+```
+
 By default, the agent's pod will complete and disappear shortly after the agent exits. In order to be able to retrieve 
 the agent's logs after it crashes, set the agent's pod's TTL to a comfortable number of seconds. This configuration can
 be specified either as a command line argument (`--agent-ttl`), environment variable (`MIRRORD_AGENT_TTL`), or in a
diff --git a/changelog.d/+agent-log-level-instructions.internal.md b/changelog.d/+agent-log-level-instructions.internal.md
new file mode 100644
index 00000000000..9514b85abcd
--- /dev/null
+++ b/changelog.d/+agent-log-level-instructions.internal.md
@@ -0,0 +1 @@
+Add instructions to CONTRIBUTING.md for changing the agent log level in mirrord config.
\ No newline at end of file