> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/configuring_nexthink/configuring-your-platform/configuring-your-platform-classic/configuring-session-performance-storage-classic.md).

# Configuring session performance storage (classic)

{% hint style="info" %}
This page applies only to the users using the classic versions of Nexthink with the Finder, Portal, and Engine components.
{% endhint %}

The session performance data is only stored if you enable it using the web interface. By default, it is disabled. When activated, the necessary settings will be automatically configured on connected Engines. It is not possible to restrict the change to a single Engine or a subset of them. Changing the parameters does not trigger a restart of the connected systems.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-424f4c5ae0eb863f07b6a52ee87a710cfc02a32b%2Fnxcheseaux-20221007-092725-20221007-072730.png?alt=media" alt="" width="544"><figcaption></figcaption></figure>

## Session performance storage management <a href="#configuringsessionperformancestorage-classic-sessionperformancestoragemanagement" id="configuringsessionperformancestorage-classic-sessionperformancestoragemanagement"></a>

To configure the storage policy, connect to the web interface as an administrator. In the main navigation bar on the left, click on the administration icon and select **Engines** under the **System configuration** section.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-da5526494eab2470a57a78b050169ec22c0414bd%2Fnxportal-1599035272.png?alt=media" alt="" width="340"><figcaption></figcaption></figure>

Check the box next to **remote sessions** if you want to store additional information related to the remote sessions connecting to a server.

Check the box next to **local sessions** if you want to store additional information related to the remote sessions using the console session.

## Impact on data retention <a href="#configuringsessionperformancestorage-classic-impactondataretention" id="configuringsessionperformancestorage-classic-impactondataretention"></a>

Activating the option to store this supplementary data on Engine impacts the amount of events stored on it, and thus the overall data retention. You should expect a typical impact of less than 5%. For example, Engine configured to store 200 million events, when full, could have up to 10 million of them linked to the session performance monitoring.

***

RELATED TOPICS

* [Engine (classic)](/references/references-classic/glossary-classic/engine-classic.md)
* [Session performance (classic)](/references/references-classic/database-information-and-organization-classic/session-performance-classic.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nexthink.com/configuring_nexthink/configuring-your-platform/configuring-your-platform-classic/configuring-session-performance-storage-classic.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.