 
   where `options` is a keyword list. The result of the call is
   the result returned by `configure_backend/2`. The recommended
-  return value for successful configuration is `:ok`.
+  return value for successful configuration is `:ok`. For example
+
+      def handle_call({:configure, options}, state) do
+        new_state = reconfigure_state(state, options)
+        {:ok, :ok, new_state}
+      end
 
   It is recommended that backends support at least the following
   configuration options:

  the `:backends` configuration into the `Logger` event manager. The event
  manager and all added event handlers are automatically supervised by `Logger`.

  Once initialized, the handler should be designed to handle events
  in the following format:

      {level, group_leader, {Logger, message, timestamp, metadata}} | :flush

  where:

    * `level` is one of `:debug`, `:info`, `:warn`, or `:error`, as previously
      described
    * `group_leader` is the group leader of the process which logged the message
    * `{Logger, message, timestamp, metadata}` is a tuple containing information
      about the logged message:
      * the first element is always the atom `Logger`
      * `message` is the actual message (as chardata)
      * `timestamp` is the timestamp for when the message was logged, as a
        `{{year, month, day}, {hour, minute, second, millisecond}}` tuple
      * `metadata` is a keyword list of metadata used when logging the message

  It is recommended that handlers ignore messages where
  the group leader is in a different node than the one where


  The initial backends are loaded via the `:backends` configuration,
  which must be set before the `:logger` application is started.
  Backends can also be added dynamically through `add_backend/2`.

  ### Console backend

