---
title: "Custom Logger Plug-in"
url: https://docs.zeroc.com/ice/3.8/plugins/custom-logger-plug-in
language: cpp
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: C++. Other languages: [C#](https://docs.zeroc.com/ice/3.8/plugins/custom-logger-plug-in/csharp.md), [Java](https://docs.zeroc.com/ice/3.8/plugins/custom-logger-plug-in/java.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 [`Ice::LoggerPlugin`](https://code.zeroc.com/ice/3.8/api/cpp/classIce_1_1LoggerPlugin.html), a plug-in that installs a logger into the communicator. Assuming you wrote a `CustomLogger` class that implements `Ice::Logger`, create a plug-in factory function that returns a `LoggerPlugin` for your logger:

```cpp
extern "C" ICE_DECLSPEC_EXPORT Ice::Plugin* createCustomLoggerPlugin(
    const Ice::CommunicatorPtr& communicator,
    const std::string&,
    const Ice::StringSeq&)
{
    return new Ice::LoggerPlugin(communicator, std::make_shared<CustomLogger>());
}
```

Then, package your `CustomLogger` implementation and `createCustomLoggerPlugin` in a shared library or DLL, and configure your communicator to load it at runtime. For example:

```config
Ice.Plugin.CustomLogger=customlogger,0:createCustomLoggerPlugin
```

With `customlogger,0`, Ice loads `customlogger0.dll` on Windows, `libcustomlogger.so.0` on Linux, and `libcustomlogger.0.dylib` on macOS. See [Ice.Plugin.name](https://docs.zeroc.com/ice/3.8/property-reference/ice-plugin-properties/cpp.md#ice.plugin.name) for the format of this entry point.

## See Also

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