From d32a98acc4e1d21b65c39cca743d430d18649882 Mon Sep 17 00:00:00 2001
From: Bryan Wilches <60490258+BryanWV@users.noreply.github.com>
Date: Thu, 1 May 2025 15:32:03 -0500
Subject: [PATCH] Update auth-logs.md

Feat: Adding new information about visualizing log info in the Debian OS
---
 .../roadmaps/linux/content/server-review/auth-logs.md  | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/src/data/roadmaps/linux/content/server-review/auth-logs.md b/src/data/roadmaps/linux/content/server-review/auth-logs.md
index 7d0911fcd..b8e7b6f39 100644
--- a/src/data/roadmaps/linux/content/server-review/auth-logs.md
+++ b/src/data/roadmaps/linux/content/server-review/auth-logs.md
@@ -9,5 +9,13 @@ Here is an example of how you can use the `tail` command to view the last few en
 ```bash
 tail /var/log/auth.log
 ```
+However, there is a newer way to see the logs in your system. In the Debian OS there is a directory called **journal** located in the /var/log. To access the collected log data it is required to use the `journalctl` command, which will output the logs.
+Here is an example of how you can use the `journalctl` command:
 
-Get yourself familiar with reading and understanding auth logs, as it's one essential way to keep your server secure.
\ No newline at end of file
+```bash
+journalctl --since "yesterday" 
+```
+The last command will display all the collected information since the day before the current day. You may want to use the man journalctl to see all the options available for this command.
+
+
+Get yourself familiar with reading and understanding auth logs, as it's one essential way to keep your server secure.