Syslog to a file

I've got the Orion syslog service set to retain messages for 30 days. I'd like to keep them longer by logging to a file but I'd also like that file to be rotated daily. It looks to me like Orion can't do that. The filename field doesn't seem to support a ${Date} variable or anything like that.

Is this correct?

If it is please take down a suggestion that the filename field take variables. Rotating logs with an outside script has always been a massive hassle.

Find more posts tagged with

syslog

suggestion

orion

Accepted answers

All comments

FormerMember

Right, we don't do this today. I've recorded it as a feature request.

torrielw

Denny, why can't we have a separate syslog server as it was before?

FormerMember

Torrie,

Although it's a little before my time, the real oldtimers around here tell me that the Syslog Server was integrated into Orion because of overwhelming customer demand. In contrast, since then, there haven't been many requests to keep a separate Syslog Server as well.

We could, of course, try to maintain both, but that decision doesn't come for free. If we maintained two Syslog Servers, we wouldn't do something else. The reason we can keep SolarWinds' products so inexpensive is that we are selective about what we do, and our metrics for selection are centered in providing the most value for the most customers (as opposed to some enterprise software companies that try to provide "cutting edge" (i.e., pricey) features that appeal primarily to the very largest customers with more to spend.)

I hate disappointing people (despite the frequency with which I do it), so that's the rationale as to why we're not giving you what you'd like.

Denny

qle

I use a batch file to rename the syslog files and then have a weekly scheduled task that executes the batch file. The batch file contains a single command:

ren [name of syslog file] %date:~10,4%%date:~4,2%%date:~7,2%.txt

This essentially renames the file to [year][month][date].txt such as 20080108.txt. The batch file does sit in the same folder as the syslog files but it's been working just fine for me.