<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Monitoring on Linux Security</title><link>https://linuxtransfer.com/tags/monitoring/</link><description>Recent content in Monitoring on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 17 Sep 2026 11:24:17 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/monitoring/index.xml" rel="self" type="application/rss+xml"/><item><title>Using grep and awk to pull per‑user SSH login failures from /var/log/auth.log into a CSV file</title><link>https://linuxtransfer.com/post/2026-09-17-using-grep-and-awk-to-pull-peruser-ssh-login-/</link><pubDate>Thu, 17 Sep 2026 11:24:17 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-09-17-using-grep-and-awk-to-pull-peruser-ssh-login-/</guid><description>&lt;p>A quick way to see who’s repeatedly failing to log in via SSH is to pull the relevant lines from &lt;code>/var/log/auth.log&lt;/code> and turn them into a CSV. The CSV can then be fed into a spreadsheet, a Grafana dashboard, or a simple shell script that alerts you when a user crosses a threshold. Below is a step‑by‑step recipe that uses only &lt;code>grep&lt;/code> and &lt;code>awk&lt;/code>, two tools that are guaranteed to be present on any modern Linux distribution.&lt;/p></description></item></channel></rss>