Selenium chromedriver disable logging or redirect it java

Ok i have managed to finally get rid of that useless loggings. Here is what i did.
Use:
System.setProperty("webdriver.chrome.silentOutput", "true");

To get rid of chromedriver logs:

Starting ChromeDriver 2.43.600233 (523efee95e3d68b8719b3a1c83051aa63aa6b10d) on port 1628 Only local connections are allowed.

And use:java.util.logging.Logger.getLogger("org.openqa.selenium").setLevel(Level.OFF);
To get rid of selenium logs:

ott 24, 2018 7:52:01 PM org.openqa.selenium.remote.ProtocolHandshake createSession INFORMAZIONI: Detected dialect: OSS

Drunk Cat's answer is right and very useful to get rid of 100's of pointless info messages in a log. Maybe use java.util.logging.Logger.getLogger("org.openqa.selenium").setLevel(Level.SEVERE);
to catch errors (Level.SEVERE instead of Level.OFF)

Chromedriver v83 (2020 Update)
Note that an alternate to setting the property:

System.setProperty(ChromeDriverService.CHROME_DRIVER_SILENT_OUTPUT_PROPERTY, "true"); 

is something like this:

DriverService.Builder serviceBuilder = new ChromeDriverService.Builder().withSilent(true);ChromeOptions options = new ChromeOptions();// ... addArguments to options ....ChromeDriverService chromeDriverService = (ChromeDriverService)serviceBuilder.build(); ChromeDriver driver = new ChromeDriver(chromeDriverService, options);

However, for whatever reason neither .withSilent(true) or setting the property work on Chromedriver v83 (confirmed on Linux and Windows). I needed to add a line of code to re-direct output:

:ChromeDriverService chromeDriverService = (ChromeDriverService)serviceBuilder.build(); chromeDriverService.sendOutputTo(new FileOutputStream("/dev/null"));ChromeDriver driver = new ChromeDriver(chromeDriverService, options);

You could just substitute "/dev/nul" with a real file if you wanted (for debugging, etc). Or a platform independent way of dealing with null output that works with Java 8+ :

chromeDriverService.sendOutputTo(new OutputStream(){@Override public void write(int b){}});

My guess is that this may be a bug in the v83 release, but at least it got me to find another way of re-directing or shutting off chromedriver logging.