> For the complete documentation index, see [llms.txt](https://wiki.datadike.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.datadike.com/product-guide/configuracoes/pam/audit/auditoria-de-logs/registro-de-logins.md).

# Registro de logins

Histórico completo de todos os logins realizados no sistema PAM. Permite monitorar tentativas de acesso bem-sucedidas e com falha, identificando possíveis ameaças de segurança.

### Colunas da Tabela

Nome de usuário: usuário que tentou fazer login. Método de autenticação: método utilizado (Senha, MFA, etc.). Descrição do motivo: detalhe sobre falhas de login (ex: "The username or password you entered is incorrect"). Status: resultado do login (Successo ou Falha). Data de login: data e hora da tentativa de acesso.

### Filtros de Pesquisa

A pesquisa pode ser feita por nome de usuario. Tambem e possivel filtrar por periodo (data de inicio e data de termino) utilizando o seletor de datas no topo da pagina. O campo de busca permite localizar tentativas de login especificas rapidamente. Os registros podem ser exportados e a tabela suporta ordenacao por qualquer coluna.


---

# 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 dynamically by asking a question.

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

```
GET https://wiki.datadike.com/product-guide/configuracoes/pam/audit/auditoria-de-logs/registro-de-logins.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.