Need some log monitoring ideas

[pzabb6]

I would like to use the built in check for monitoring log files (log[file<,regexp>])

There are two conventions for our logs:
1.) C:\logs\<YYYY-MM-DD>\someprocess\someprocess.log
2.) C:\logs\<YYYY-MM-DD>\someprocess\someprocessHHMMSS.log (where the process appends the time it starts to the end of the file
name)


Is it possible to use the built in log monitoring function to monitor these logs? Is there a macro that can be used to get the date in that format for the first convention?

Is it possible to create a UserParameter that passes the log path to the key? This is probably a stretch...
-example:
- 1) Create a user parameter - UserParameter=GetLogFile[],cscript getLogFile.vbs
- 2) Create an item with key = log[GetLogFile[],Fail]

Any ideas or suggestions would be appreciated.

Thanks

[buffboi82]

I would like to use the built in check for monitoring log files (log[file<,regexp>])

There are two conventions for our logs:
1.) C:\logs\<YYYY-MM-DD>\someprocess\someprocess.log
2.) C:\logs\<YYYY-MM-DD>\someprocess\someprocessHHMMSS.log (where the process appends the time it starts to the end of the file
name)


Is it possible to use the built in log monitoring function to monitor these logs? Is there a macro that can be used to get the date in that format for the first convention?

Is it possible to create a UserParameter that passes the log path to the key? This is probably a stretch...
-example:
- 1) Create a user parameter - UserParameter=GetLogFile[],cscript getLogFile.vbs
- 2) Create an item with key = log[GetLogFile[],Fail]

Any ideas or suggestions would be appreciated.

Thanks

Hummm... I am not sure if any built-in checks would work............................

[pzabb6]

A solution to the first convention would be enough to make this the right solution for our firm.

[jroberson]

I'm not sure Zabbix has the capability to do that. The real problem is the format

1.) C:\logs\<YYYY-MM-DD>\...

and

...\someprocessHHMMSS.log ...

Zabbix has no built in Macros or another way to change the path or name of the file to be read, that I know of, at least. A solution would be a script that will read the log file (you would call it from a UserParameter entry) and either return the text or just an error flag if it sees an offending entry. You can use Flexible User Parameters to pass the script a file/path name if needed (Zabbix Manual 1.6 pg 120). Another possible solution would be to implement rolling log files instead of using time/date stamped log file paths and names. It would depend on what your particular software supports. There might be more ways, but those are the only two I could think of.

[pzabb6]

I've been getting around this by using directory junctions in windows. Its a directory symbolic link for windows.

The agent had problems with symbolic links (mklink) to files in Server 2008