> 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/pt/portal-de-administracao/settings/log-exporter/log-analytics.md).

# Análise de registos

## Pré-requisitos

Para ingerir registos do RADIUSaaS num **Área de Trabalho do Azure Log Analytics**, certifique-se de que um workspace já foi criado e de que tem os seguintes **valores obrigatórios** disponíveis:

* ID do cliente
* Chave partilhada
* Nome do evento

## Passos de configuração

Siga estes passos para adicionar um **Log Analytics** destino de exportação:

* Navegue até ao seu **Portal de Administração do RADIUSaaS**
* Clique em **+ Destino de exportação**
* Selecione **Exportador do Azure Log Analytics**
* Forneça um **Nome** e **Descrição**
* Configure o **Filtros de mensagens** às suas necessidades
* Estruture os **Dados** a serem ingeridos no seu Log Analytics Workspace

{% hint style="warning" %}
Alguns dados que poderá enviar para o seu Log Analytics workspace incluirão caracteres de nova linha. \
Para obter um JSON válido para cada entrada, o motor de templates tem um **tojson** **parser** que será aplicado a todas as variáveis a que aceder. 

Por conseguinte, **não coloque aspas em nenhuma variável jinja**.
{% endhint %}

**Correto**

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

**Errado**

![](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/pt/portal-de-administracao/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.