Does anyone have any suggestions for a server log viewer? My server's logs are so clogged up with daily mundane-ness that if there ever was something there I should see, I would likely never see it because it's hiding in the mass of log entries.

What I'd like to be able to do is omit common/known items from the log so that uncommon/un-known items are the only thing I see. When I say omit, I mean omit from view, not omit from the log entirely.

Also, what I am referring to when I say daily mundane-ness/common/known items is these types of entries:

Schedule "AutoMailer" running

Schedule "AutoMailer" has started FileMaker script "AutoMailer"

Client "AutoMailer" authentication failed on (axillary database file, which is auto-logged on)

Schedule "AutoMailer" scripting error (401)

Schedule "AutoMailer" completed

Schedule "AutoMailer" scheduled for (3 min. from now)

I get the above group of log entries every 3 min.

export to CSV, build your own in FM...

provided that the built-in filtering in the Windows Event Viewer doesn't do it for you.

What Wim said. The logs are specifically designed to be imported into a FileMAker Pro database.

Steven

First off, I forgot to mention the server is running on a Mac, I am not that familiar with Mac's so maybe there are filtering tools in the console I am un-aware of?

I thought that building a database might be the solution, and was already thinking of how I'd like to build it...

I would prefer to not have to import records into the database every time I want to view the log. I was hoping it was something I could script on the server. I read your post on server side imports, which said you can only import from Documents or Temp folder. Any ideas on how I could copy the log file to either of these folders? (or at least the part of the log that changed since last script run)

Actually, I just thought of one... I could run a combination System level script then FM script. The OS script might be able to use 'tail' or something similar to retrieve only the part of the log file that changed since last import. Not sure if I can actually do that with 'tail' though: any other ideas?

You've got the right concept: a FMS script sequence schedule will let you do some OS-level scripting (shell or applescrpt in your case) followed by a FM script. If you exit your shell script or applescript with anything but exit code 0 then the FM script will not run.