given this information:

Code:

^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[[[:digit:]]+\.[[:digit:]]+\])? [[:alnum:]]+: media error \(bad sector\): status=0x[[:xdigit:]]+ { DriveReady SeekComplete Error }$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[[[:digit:]]+\.[[:digit:]]+\])? end_request: I/O error, dev [[:alnum:]]+, sector [[:digit:]]+

i need to set up monitoring for these strings. but as you can see, they contain characters that some applications (i.e. Nagios ) will have issues processing as it considers them potentially risky.

so, will the following changes suffice?

Code:

kernel:.*media error.*bad sector.*status=0x.*DriveReady.*SeekComplete.*Error 
kernel:.*end_request: I/O error, dev.*sector

i basically just got rid of any character i think Nagios may complain about. and i replaced it with ".*". note, each of these strings will be passed to either egrep or awk to scan a log.

can any one of you experts please help point out what may be wrong with what i just did?