---
title: "configureSessionLog"
slug: "api/session/operations/configuresessionlog"
sidebar:
  order: 163
---

<a id="ref-2c2afe1f3bf0"></a>
<a id="ref-b1e0ec58f0c3"></a>
<a id="ref-9e8c6a3e53ed"></a>

## Synopsis

```text
void configureSessionLog(SessionId sessionId,
    boolean enable,
    LogConfig *config)
throws SessionServiceFault;
```

See also: [`SessionId`](/pCon/configuratorOnline/specs/api/session/types/sessionid#ref-02e397c8fdb4), [`LogConfig`](/pCon/configuratorOnline/specs/api/session/types/logconfig#ref-37143a229e80), [`SessionServiceFault`](/pCon/configuratorOnline/specs/api/session/faults/sessionservicefault#ref-30a5c7817f4a)

The operation enables/disables and configures logging of session-specific log messages.

Instead of a session ID the operation can also be invoked with a session context ID as their first argument (see also §[newSessionContext](/pCon/configuratorOnline/specs/api/session/operations/newsessioncontext#ref-71351064821d)). If so, the session ID stored in the session context will be used as the actual session ID. The changes will be made for the whole session including all projects loaded in the session.

Log messages generated during the execution of a web-service operation that specifies a session ID may be stored in a session-specific buffer for later retrieval by the client. To enable this feature, `configureSessionLog` must called with parameter `enable` set to true.

If parameter `enable` is true, the optional parameter `config` may be used to adjust some properties of the session log handler and to select a subset of the session-specific log-messages to be stored in the session log buffer.

All parameters are optional. If not specified, their default values (or previous values in case of repeated calls of `configureSessionLog` with `enable` set to true) will be used. A call of `configureSessionLog` with `enable` set to false will revert all previously set parameters to their default vaues.
