[Tutorial] How to detect server console output

Hi there.
This is a tutorial on how to detect any console outputs from the server.

You need to get the Bukkit Logger and add a Handler.
That looks like this:

Code:

Bukkit.getServer().getLogger().addHandler(new Handler() {
            @Override
            public void close() throws SecurityException {/*Ignore this method*/}
 
            @Override
            public void flush() {/*Ignore this method*/}
 
            @Override
            public void publish(LogRecord logRecord) {
                //Do something with the logRecord
                //Interesting methods of the logRecord object may be:
                logRecord.getLevel().toString();//SEVERE / WARNING / INFO etc
                logRecord.getMillis();      //The the unix timestamp of the logRecord
                logRecord.getMessage();        //The logged message
            }
        });

You can ignore the close() and flush() methods.
The publish() method is always called when a console output is done.

IMPORTANT: It's important to import java.util.logging.Handler and not javax.xml.ws.Handler

If you have any questions on this feel free to leave a question or a comment.

 

Thank you! !

 

What do you mean by "almost everything"?
Do you mean add handlers for nearly all bukkit proccesses

 

Yes, you can.
That's what makes bukkit so awesome!

 

If you set a LogRecord to Level.OFF, shouldn't that keep the message from going to console? I'm trying to remove "Processing Shard" from my FTB server.

 

Well, maybe it keeps the message from being shown in the console but it will show up in the server.log file.

 

It still does show up in console, that's my problem xP

 

jb_aero I think you can use a filter for that. The only problem is that you can only set one filter for every logger. So if another plugin or Bukkit already is using it it will be overwriten. I'm not sure but you can try it:

Code:java

Bukkit.getServer().getLogger().setFilter(new java.util.logging.Filter() {
  @Override
  public boolean isLoggable(LogRecord log) {
    // Return if the logger should log it
    return true;
  }
});

 

A log handler?

 

Ah... But why do you post this here?

 

Ah lol

 

Well, this problem is related to FTB.
This tutorial is only about how to detect the console output.
You have to contact FTB or sth like that and ask them for don't log everything.

 

And for remove it ?

 

Minecrell 's Filter tip did the trick actually

 

Yes.

 

Remember to remove the handler at the onDisable() or you get your self a memory leak.

Also, a fun note, the close is called when the server owners shuts down the server wrong, but not if they use the stop, you can use this to detect crashes that terminate the java process

 

Yes. That's important. But I think that if the server shuts down there is not really time for something like memory leaks.
But still everybody should use it.

 

So that could be used to save stuff that should be saved on close that wasn't due t negligent server admin? (Eg, donors, voters)

 

Yes. But if you are using sometihng like an outputstream to write to a file you wouldn't jave to save it. You'd only have to close the outputStream.

 

Yeah, I know. I am just saying its a possible use case.

 

Thanks a lot for this code!

 

MinecraftShamrock Doesn't work for 1.7.9, or do I use the wrong code?

Code:

package play.mickedplay.clr;
import java.util.logging.Handler;
import java.util.logging.LogRecord;
import org.bukkit.Bukkit;
import org.bukkit.plugin.java.JavaPlugin;
public class CLR extends JavaPlugin
{
 public void onEnable()
 {
  Bukkit.getServer().getLogger().addHandler(new Handler()
  {
            @Override
            public void close() throws SecurityException
            {}
 
            @Override
            public void flush()
            {}
 
            @Override
            public void publish(LogRecord logRecord)
            {
                //Do something with the logRecord
                //Interesting methods of the logRecord object may be:
                logRecord.getLevel().toString();//SEVERE / WARNING / INFO etc
                logRecord.getMillis();      //The the unix timestamp of the logRecord
                logRecord.getMessage();        //The logged message
            }
        });
 }
 
 public void onDisable()
 {
  
 }
}

 

Try using this instead; 1.7.x introduced Log4J which replaced this.

Code:java

       Logger logger = (Logger) LogManager.getRootLogger();
        logger.setLevel(Level.ALL);
        logger.addFilter(hijackFilter = new Filter() {
 
            @Override
            public Result filter(LogEvent event){
                //do stuff with event
                return null;
            }
 
            @Override
            public Result filter(Logger paramLogger, Level paramLevel, Marker paramMarker, String paramString, Object... paramArrayOfObject){
                return null;
            }
 
            @Override
            public Result filter(Logger paramLogger, Level paramLevel, Marker paramMarker, Object paramObject, Throwable paramThrowable){
                return null;
            }
 
            @Override
            public Result filter(Logger paramLogger, Level paramLevel, Marker paramMarker, Message paramMessage, Throwable paramThrowable){
                return null;
            }
 
            @Override
            public Result getOnMatch(){
                return null;
            }
 
            @Override
            public Result getOnMismatch(){
                return null;
            }
 
        });