3 ms·
A while back, someone (here, I think) cited an article / blog entry wherein the author describes his log reading process as first filtering out all the... I'll
by pasbesoin 17y ago
A while back, someone (here, I think) cited an article / blog entry wherein the author describes his log reading process as first filtering out all the... I'll use the word "typical" entries. He identified patterns for these and lets a script strip these out. As he continues to identify those types of entries, he adds patterns for them to the script.
He then focuses on what remains. At least as described, it sounded like an effective way to focus attention on the needles in the haystack.
Note that this doesn't mean shrinking your logs. It means an automated process for extracting an interesting subset. You still have the complete logs for other work. I'd also regularly audit the extract process both for sufficiency and as a reminder that its output is not the only thing you should be paying attention to.
It's not my idea, and I'm probably not doing it justice. Maybe someone else recalls the article / blog entry and has a link. It's also not something I need to do; perhaps if I did, I'd see shortcomings in the methodology.
- shykes 17y ago> [...] first filtering out all the... > I'll use the word "typical" entries. > He identified patterns for these and > lets a script strip these out. As he continues > to identify those types of entries, he adds > patterns for them to the script. > He then focuses on what remains. That's exactly what logcheck does. http://logcheck.org http://logcheck.org