> For the complete documentation index, see [llms.txt](https://docs.akamas.io/akamas-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akamas.io/akamas-docs/3.5.0/using/study/live-optimization-studies/analyzing-results-of-live-optimization-studies.md).

# Analyzing results of live optimization studies

Even for live optimization studies, it is a good practice to analyze how the optimization is being executed with respect to the defined goal & constraints, and workloads.

This analysis may provide useful insights about the system being optimized (e.g. understanding of the system dynamics) and about the optimization study itself (e.g. how to adjust optimizer options or change constraints). Since this is more challenging for an environment that is being optimized live, a common practice to adopt a recommendation mode before possibly switching to a fully autonomous mode.

The Akamas UI displays the results of an offline optimization study in the following areas:

* the **Metrics section** (see the following figures) displays the behavior of the metrics as configurations are recommended and applied (possibly after being reviewed and approved by users); this area supports the analysis of how the optimizer is driven by the configured safety and exploration factors.

<figure><img src="https://3774185011-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJSNpKvJ3IYa5Vo69I0ed%2Fuploads%2Fgit-blob-c31bebb2468d83b30cf7834760660eaa8d4da17e%2FScreenshot%202023-01-25%20at%2023.11.09.png?alt=media" alt=""><figcaption><p>Metrics section of a live optimization study</p></figcaption></figure>

<figure><img src="https://3774185011-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJSNpKvJ3IYa5Vo69I0ed%2Fuploads%2Fgit-blob-84b1a4fe070555555a3dc0a565ea2a52526259a7%2FScreenshot%202023-01-25%20at%2019.20.00.png?alt=media" alt=""><figcaption><p>From the metrics cahrt displaying configurations (toggle on) to a specific configuration</p></figcaption></figure>

* The **All Configurations** section provides the list of all the recommended configurations, possibly as modified by the user, as well as the details of each applied configuration (see the following figures).

<figure><img src="https://3774185011-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJSNpKvJ3IYa5Vo69I0ed%2Fuploads%2Fgit-blob-4d76134a48bf055645734467e3f5821b091a43a9%2FScreenshot%202023-01-25%20at%2023.21.02.png?alt=media" alt=""><figcaption><p>The list of configurations applied ovet time in the All Configuration section</p></figcaption></figure>

<figure><img src="https://3774185011-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJSNpKvJ3IYa5Vo69I0ed%2Fuploads%2Fgit-blob-d290ec7ef3215a650a10c9680701a47cf756e583%2FScreenshot%202023-01-25%20at%2019.19.11.png?alt=media" alt=""><figcaption><p>A specifici configuration from the All Configuration section</p></figcaption></figure>

* in the case of a recommendation mode, the **Pending configuration** section (see the following figure) shows the configuration that is being recommended to allow users to review it (see the EDIT toggle) and approve it:

<figure><img src="https://3774185011-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJSNpKvJ3IYa5Vo69I0ed%2Fuploads%2Fgit-blob-2730853f93a58e608f663b3953a7954365d983a0%2FScreenshot%202023-01-25%20at%2019.18.58.png?alt=media" alt=""><figcaption><p>Pending configutation</p></figcaption></figure>


---

# 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.akamas.io/akamas-docs/3.5.0/using/study/live-optimization-studies/analyzing-results-of-live-optimization-studies.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.