# Overview

## System Description Page

This page gives an overview of the high level system structure as configured in the config yaml file. The yaml file is reloaded every time the page is refreshed, so it is usefull to debug the yaml config file.

Every system component has a key, a type and a description. External database components have type jdbc.

 If the system is deployed in multiple environments, you can configure a list of different environments, each with a key and description.

![](https://2718803548-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LWAEKm9JcXd3RYhXC5W%2F-LlpbltTSXoNh5uwp0aa%2F-Llpbo_Z3uW8wFSkItk4%2Fsystemdescription-0.0.3.png?alt=media\&token=0c99e07b-e4c7-4de8-979f-3f054e939976)

## System Connections Page

This page gives an overview of the connection settings of each subsystem,  grouped in tabs by environment.  You can validate the connection settings for an environment by clicking the connectivity test button.

![](https://2718803548-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LWAEKm9JcXd3RYhXC5W%2F-LlpcVu_pSFWqMSe-2_K%2F-LlpcYPx9SP4j8xFaHmS%2Fsystemconnections-0.0.3.png?alt=media\&token=58634694-ba5d-462e-bfbe-00ae15a457b5)

## Recordings Page

This page lists recordings and shows metadata of each recording like environment and creation date. From this page you can start a new recording or open an existing recording.

![](https://2718803548-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LWAEKm9JcXd3RYhXC5W%2F-LkxE-wX2UJkD85IPuIm%2F-LkxHNc0w0jmMjMgvQqq%2Frecordings.png?alt=media\&token=757aa98d-a060-4d45-be72-5775d0cce6aa)

## Recording Page: initial state, final state

After clicking the "Take snapshot" button for the first time, the recording panel contains an **initial state**,  a full snapshot of all the system components.

 For jdbc components the full snapshot view consists of a dump of all the data in all the tables as specified in the yaml config file. 

After some interacting with the system additional snapshots can be taken to see how the system state has changed. 

Only the initial state and the **final state** are presented as a full snapshot. The intermediary snapshots are presented as **deltas**

![Database snapshot](https://2718803548-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LWAEKm9JcXd3RYhXC5W%2F-LkxE-wX2UJkD85IPuIm%2F-LkxHOt_Zok7mO4QFMd3%2Frecording01.png?alt=media\&token=344f50a0-a104-4676-94f4-465fb05ab56f)

![File system snapshot](https://2718803548-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LWAEKm9JcXd3RYhXC5W%2F-LlpeTbCYlkYq5aHy0sX%2F-LlpfL7a9-gmlGXM9GSm%2Frecording-filesystem-snapshot-0.0.3.png?alt=media\&token=8bcec30c-769a-499b-adc4-95da1ba2a800)

## Recording page: deltas between snapshots

 The intermediary states (i.e. initial nor final state) are presented as **deltas** between consecutive snapshots. 

For jdbc components a delta view consists of a **summary card** with total number of inserts/updates/deletes , and a **detailed delta view** of the changed table rows with a **row delta indicator**

| Indicator | Row      |
| --------- | -------- |
| I         | Inserted |
| U         | Updated  |
| D         | Deleted  |

![delta between DB snapshots](https://2718803548-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LWAEKm9JcXd3RYhXC5W%2F-LkxE-wX2UJkD85IPuIm%2F-LkxHPtLvCpK7gxGmqOR%2Frecording02.png?alt=media\&token=6878fb18-d738-4c5c-b3aa-24467327206d)

![delta between file system snapshots](https://2718803548-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LWAEKm9JcXd3RYhXC5W%2F-LlqlMdUipaXzGJewjpc%2F-Llqn9Yy5-UeF7kb-QXN%2Frecording-filesystem-delta-0.0.3.png?alt=media\&token=f4240678-b52f-407e-bcc5-8b703bfb6845)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://driftserver.gitbook.io/drift-server/use/untitled.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.