From 4a490a013e3b4aa3f7d36845d70d4b4b3a2fe24c Mon Sep 17 00:00:00 2001
From: Wolmin <44748271+Wolmin@users.noreply.github.com>
Date: Tue, 10 Oct 2023 19:09:33 +0200
Subject: [PATCH] Feature: CLI status peers command (#666)

* Add information about status peers command

* Fix typo

* Fix linter

* Fix linter

* Fix linter
---
 docs/networks/mainnet/running-a-node.md | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/docs/networks/mainnet/running-a-node.md b/docs/networks/mainnet/running-a-node.md
index cfe5540858..bd22d35200 100644
--- a/docs/networks/mainnet/running-a-node.md
+++ b/docs/networks/mainnet/running-a-node.md
@@ -157,7 +157,21 @@ lukso status
 # INFO[0000] PID 39432 - Validator (validator): Stopped 🔘
 ```
 
-If you want to check any of the running clients in more detail, you can use the built-in logging command of the CLI. It will print out the current log messages of one client to the terminal screen.
+You can also check the connectivity of your clients by running `lukso status peers` command - this will show how many
+peers are your clients connected with.
+
+```bash
+lukso status peers
+
+# INFO[0000] Execution (Geth): Outbound: 10 | Inbound: 3 🟢
+# INFO[0000] Consensus (Lighthouse): Outbound: 5 | Inbound: 8 🟢
+```
+
+Please note that execution client may need additional APIs enabled in order to send peer info. You can read more on how
+to enable those [here](https://github.com/lukso-network/tools-lukso-cli#how-to-get-your-peer-count).
+
+If you want to check any of the running clients in more detail, you can use the built-in logging command of the CLI. It
+will print out the current log messages of one client to the terminal screen.
 
 ```bash
 # Viewing the logs of the execution client