January/February 2018 issue of acmqueue

The January/February issue of acmqueue is out now

System Administration

  Download PDF version of this article PDF

ITEM not available


Originally published in Queue vol. 9, no. 1
see this item in the ACM Digital Library



Adam Oliner, Archana Ganapathi, Wei Xu - Advances and Challenges in Log Analysis
Logs contain a wealth of information for help in managing systems.

Christina Lear - System Administration Soft Skills
How can system administrators reduce stress and conflict in the workplace?

Thomas A. Limoncelli - A Plea to Software Vendors from Sysadmins - 10 Do's and Don'ts
What can software vendors do to make the lives of sysadmins a little easier?

Eben M. Haber, Eser Kandogan, Paul Maglio - Collaboration in System Administration
For sysadmins, solving problems usually involves collaborating with others. How can we make it more effective?


(newest first)

Florian Heigl | Sat, 24 Mar 2012 00:24:23 UTC

The only thing were this made me disagree is the notion that system administrators aren't fully aware of those issues. We are just in a situation where we get delivered with software that is usually unmaintainable written by people who most do not care. Either you got no logs, broken logs, logs that DO NOT LOG IF SOMETHING GOES WRONG or log4j logs that nothing more than a application trace and usually has 10%+ of messages that are wrongly classified, or, the thing i love most, people who think that a python backtrace is error handling. This is why we insist on seeing a system built in the isolated lab, so that we can build filters that represent the "normal application behaviour" and can immediately recognize when it goes to hell. Adding more and more log datapoints is and splunking the data is a nice help, but not enough; and that's where i'm back to agreeing: we all need to get better in building systems that are planned on the notion that failure can happen.

Leave this field empty

Post a Comment:

© 2018 ACM, Inc. All Rights Reserved.