I’m trying to set up a script where an alert is generated when a certain string appears in a log file.
The solution already in place greps the whole log file once a minute and counts how often the string appears, using the log line’s timestamp to count only occurrences in the previous minute.
I figured it would be much more efficient to do this with a tail, so I tried the following, as a test:
FILENAME="/var/log/file.log"
tail -f $FILENAME | awk -F , -v var="$HOSTNAME" '
BEGIN {
failed_count=0;
}
/account failure reason/ {
failed_count++;
}
END {
printf("%saccount failure reason (Errors per Interval)=%d\n", var, failed_count);
}
'
but this just hangs and doesn’t output anything. Somebody suggested this minor change:
FILENAME="/var/log/file.log"
awk -F , -v var="$HOSTNAME" '
BEGIN {
failed_count=0;
}
/account failure reason/ {
failed_count++;
}
END {
printf("%saccount failure reason (Errors per Interval)=%d\n", var, failed_count);
}
' <(tail -f $FILENAME)
but that does the same thing.
The awk I’m using (I’ve simplified in the code above) works, as it’s used in the existing script where the results of grep “^$TIMESTAMP” are piped into it.
My question is, how can get the tail -f to work with awk?
Assuming your log looks something like this:
you could do something like this:
Note that I’ve changed this to
tail -F(capital F) because it handles log aging. This isn’t supported in every operating system, but it should work in modern BSDs and Linuces.How does this work?
Awk scripts consist of sets of
test { commands; }evaluated against each line of input. (There are two special tests,BEGINandENDwhose commands run when awk starts and when awk ends, respectively. In your question, awk never ended, so theENDcode was never run.)The script above has three of test/command sections:
NR == 1is a test that evaluates true on only the first line of input. The command it runs creates the initial value for thelastvariable, used in the next section./account failure reason/, we increment our counter.Clear as mud? 🙂