Dee-Ann LeBlanc | RSS

Dee-Ann LeBlanc is a technical writer, tech journalist, editor, course developer, speaker, and trainer specializing in Linux, open source, content management systems, and OS X.

Jul 30, 2010

Much of performance improvement, security, and troubleshooting work is reactive. While there’s no avoiding this fact, implementing a Daily Log Review policy puts IT staff in a more pro-active position, using each day to build a set of rules that alert you to potential problems before they become serious.

How often does your team find, while troubleshooting an issue, that were small warning signs leading up to the incident but no one had noticed, or there had been no context to make it clear that they were seeing a real problem? Hopefully you don’t encounter such situations very often, but it happens. A daily log review policy can help to catch some of these issues earlier before they bog down or, worse, break your servers.

One advantage to allocating time for daily log review into your staff’s routines is that they become more familiar with the day to day workings of your systems. This knowledge in turn makes unusual occurrences stand out even more than they would have before. READ MORE

Want more like this? Sign up for the weekly IT Expert Voice Newsletter so you don't miss a thing!
Jul 27, 2010

If you think a problem with an open source program is slowing you down, here’s how to work with the development team to get it fixed.

It sometimes happens, usually at the worst possible time. You’re investigating a performance issue with an application or server, and you realize that no amount of tuning can save you. The urge to toss the software out and start over might be strong, but such a decision can be costly and even unnecessary.

If the culprit in your performance problems is a free open source software package, there’s no need to assume that these issues can’t be fixed. After all, free isn’t a bargain if you’re not reaching the minimum levels of “fast enough for our needs.”

This article won’t lecture you on the wonders of fixing bugs yourself, though of course that’s an option with open source. If you wanted to write your own software, you’d have already done it yourself or paid someone to do it. Instead, you can, and should, communicate with the open source project’s developers to ensure that the application performance issues are addressed. READ MORE

Want more like this? Sign up for the weekly IT Expert Voice Newsletter so you don't miss a thing!
DELL
FM IT Expert Voice is a partnership between Dell and Federated Media. Privacy Statement