> For the complete documentation index, see [llms.txt](https://docs.radiusaas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.radiusaas.com/admin-portal/settings/log-exporter/log-analytics.md).

# Log Analytics

## Prerequisites

To ingest RADIUSaaS logs into an **Azure Log Analytics Workspace**, please make sure that a workspace was already created and that you have the following **required values** available:

* Customer ID
* Shared Key
* Event Name

## Configuration steps

Follow these steps to add a **Log Analytics** export target:

* Navigate to your **RADIUSaaS Admin Portal**
* Click **+ Export Target**
* Select **Azure Loganalytics Exporter**
* Provide a **Name** and **Description**
* Configure the **Message Filters** to your needs
* Structure the **Data** to be ingested into your Log Analytics Workspace

{% hint style="warning" %}
Some data which you might send to your Log Analytics workspace will include new line characters. \
To get a valid JSON for every entry, the template engine has a global **tojson** **parser** which will apply for all variables you access.&#x20;

Therefore, **do not quote any jinja variable**.
{% endhint %}

**Correct**

![](https://content.gitbook.com/content/SWU1DQ4UGkqER7uGNUOm/blobs/uq6Vayq4Wd4RpxGmp27v/image.png)

**Wrong**

![](https://content.gitbook.com/content/SWU1DQ4UGkqER7uGNUOm/blobs/5Ls36VIs0q8sUjHGDyra/image.png)


---

# 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.radiusaas.com/admin-portal/settings/log-exporter/log-analytics.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.
