Log4j logging threshold

Question

Current logging threshold that is all about log level(TRACE, DEBUG, INFO, WARN, ERROR and FATAL) is not enough for me. I have a gigabytes of log written from third party libraries into ERROR category in emergency case. I do not want to turn of this logging cause I want to see this problem logs. Most of logs are continuously repeating stack traces. So I want a kind of appender which will

1)Skip logs if threshhold(kb/sec) is reaсhed (I mean when we are writing to much logs - we might skip some) or
2)Skip stacktraces printing if more then one(n) stacktrace was printed in period of time

Please suggest

cherouvim cherouvim · Accepted Answer · 2013-11-17T08:03:13

I've written something similar in the past (sends up to X mails per Y time). It'll give you a direction. The setters are not mandatory but they allow you to change the defaults via log4j.properties.

public class LimitedSMTPAppender extends SMTPAppender {

    private int limit = 10;           // max at 10 mails ...
    private int cycleSeconds = 3600;  // ... per hour

    public void setLimit(int limit) {
        this.limit = limit;
    }

    public void setCycleSeconds(int cycleSeconds) {
        this.cycleSeconds = cycleSeconds;
    }

    private int lastVisited;
    private long lastCycle;

    protected boolean checkEntryConditions() {
        final long now = System.currentTimeMillis();
        final long thisCycle =  now - (now % (1000L*cycleSeconds));
        if (lastCycle!=thisCycle) {
            lastCycle = thisCycle;
            lastVisited = 0;
        }
        lastVisited++;
        return super.checkEntryConditions() && lastVisited<=limit;
    }

}

Log4j logging threshold

2 Answers