---
title: "Custom Logger Plug-in"
url: https://docs.zeroc.com/ice/3.8/plugins/custom-logger-plug-in
language: java
docs_index: https://docs.zeroc.com/llms.txt
---

> For an index of every page, see [llms.txt](https://docs.zeroc.com/llms.txt).

# Custom Logger Plug-in

Programming language: Java. Other languages: [C++](https://docs.zeroc.com/ice/3.8/plugins/custom-logger-plug-in/cpp.md), [C#](https://docs.zeroc.com/ice/3.8/plugins/custom-logger-plug-in/csharp.md), [JavaScript](https://docs.zeroc.com/ice/3.8/plugins/custom-logger-plug-in/js.md), [MATLAB](https://docs.zeroc.com/ice/3.8/plugins/custom-logger-plug-in/matlab.md), [PHP](https://docs.zeroc.com/ice/3.8/plugins/custom-logger-plug-in/php.md), [Python](https://docs.zeroc.com/ice/3.8/plugins/custom-logger-plug-in/python.md), [Ruby](https://docs.zeroc.com/ice/3.8/plugins/custom-logger-plug-in/ruby.md), [Swift](https://docs.zeroc.com/ice/3.8/plugins/custom-logger-plug-in/swift.md).

When you create a communicator in your own code, install a custom logger by setting `InitializationData.logger`.

A logger plug-in installs a custom logger through configuration, during communicator initialization. Use a logger plug-in when you don't create the communicator yourself, for example in an IceBox service, or when you want to install a custom logger without changing any source code.

Adding a logger plug-in factory to `InitializationData.pluginFactories` works too, but it is more work for the same result as setting `InitializationData.logger`.

## Installing a Custom Logger

Ice provides [`com.zeroc.Ice.LoggerPlugin`](https://code.zeroc.com/ice/3.8/api/java/com.zeroc.ice/com/zeroc/Ice/LoggerPlugin.html), a plug-in that installs a logger into the communicator. The communicator takes ownership of the logger and closes it when the communicator is destroyed.

Assuming you wrote a `CustomLogger` class that implements `com.zeroc.Ice.Logger`, create a plug-in factory that returns a `LoggerPlugin` for your logger:

```java
package com.example.clearsky;

import com.zeroc.Ice.Communicator;
import com.zeroc.Ice.LoggerPlugin;
import com.zeroc.Ice.Plugin;
import com.zeroc.Ice.PluginFactory;

public class CustomLoggerPluginFactory implements PluginFactory {
    @Override
    public String getPluginName() {
        return "CustomLogger";
    }

    @Override
    public Plugin create(Communicator communicator, String name, String[] args) {
        return new LoggerPlugin(communicator, new CustomLogger());
    }
}
```

Then, package your `CustomLogger` implementation and `CustomLoggerPluginFactory` in a JAR file, and configure your communicator to load it at runtime. For example:

```config
Ice.Plugin.CustomLogger=customlogger.jar:com.example.clearsky.CustomLoggerPluginFactory
```

## See Also

- [Custom Loggers](https://docs.zeroc.com/ice/3.8/administration/logger-facility/custom-loggers/java.md)
- [The Per-Process Logger](https://docs.zeroc.com/ice/3.8/administration/logger-facility/per-process-logger/java.md)
- [Plug-in Facility](https://docs.zeroc.com/ice/3.8/plugins/plug-in-facility/java.md)
- [Ice.Plugin.\*](https://docs.zeroc.com/ice/3.8/property-reference/ice-plugin-properties/java.md)
