⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Linux & SRE Interview Questions Scenario 107 of 135 in Linux & SRE
Senior DevOps / SRE [L2] Linux Syslog & Daemon Logging Production Scenario [L2]
🎯 Target Role / Context: Linux Scenario #67 (L2) · Allow user 'deploy' to restart nginx and read syslog only

Q: Application logs are written to syslog, but the logs for your specific application are mixed with system messages in `/var/log/messages`. How do you configure rsyslog to send your application's logs to a separate file?

rsyslog is the standard syslog implementation on most Linux distributions. It uses rules in /etc/rsyslog.conf or /etc/rsyslog.d/*.conf to route log messages based on facility, severity, or program name.

#Linux #Logging #Rsyslog #L2 #SRE
🎙️ Candidate Opening & Architectural Context
""We encountered this OS-level bottleneck during peak traffic and diagnosed it down to kernel and filesystem metrics. The interviewer is testing: Syslog configuration, log routing, rsyslog filters.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: "We encountered this OS-level bottleneck during peak traffic and diagnosed it down to kernel and filesystem metrics. The interviewer is testing: Syslog configuration, log routing, rsyslog filters.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

rsyslog is the standard syslog implementation on most Linux distributions. It uses rules in /etc/rsyslog.conf or /etc/rsyslog.d/*.conf to route log messages based on facility, severity, or program name.

  • Create a filter rule in /etc/rsyslog.d/myapp.conf:
  • Alternative using facility:
  • Restart rsyslog: systemctl restart rsyslog
2️⃣

Remediation & Permanent Safeguards

To separate your application's logs: The & stop directive prevents the message from also being written to /var/log/messages. If the app uses local0 facility:

# Route all messages from 'myapp' to its own file
   if $programname == 'myapp' then /var/log/myapp.log
   & stop
  • Set up logrotate for the new file in /etc/logrotate.d/myapp:
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Create a filter rule in /etc/rsyslog.d/myapp.conf:."
⚡ 60-Second Elevator Pitch Talking Points
  • Create a filter rule in /etc/rsyslog.d/myapp.conf:
  • Alternative using facility:
  • Restart rsyslog: systemctl restart rsyslog
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring Application logs written SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
  2. Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring Application logs written Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (df -h) shows ample free space.
  3. Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring Application logs written Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
  4. Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring Application logs written Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (pid_max).
Advertisement
Want more Linux & SRE scenarios?
Explore our complete collection of scenario-based Linux & SRE interview runbooks.
Browse All Linux & SRE Questions →