> For the complete documentation index, see [llms.txt](https://guia.fenicio.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guia.fenicio.help/contenido-general/log-sistema.md).

# Log Sistema

> **🖱️**Ingresa a la opción **Administración** ➡ **Logs y alertas**
>
> **🔑** Rol requerido **➡** **Logs y alertas**

## Módulo de Log / Registro de acciones

### 1. Descripción general

Este módulo **registra automáticamente todas las acciones realizadas desde la plataforma**, permitiendo llevar un seguimiento detallado de las operaciones realizadas.

### 2. Funcionalidades principales

* **Filtrado de registros:** se pueden filtrar los logs por **contenido** o por **fecha** para encontrar acciones específicas.
* **Ver detalle:** al seleccionar esta opción se mostrará el **código de la acción** realizada.
* **Tipos de acciones registradas:**
  * Comunicaciones con medios de pago
  * Envíos y respuestas
  * Despachos logísticos
  * Tasas de cambio
  * Otras acciones realizadas dentro de la plataforma

### 3. Uso recomendado

* Utilizar los filtros para **acceder rápidamente a la información relevante**.
* Revisar los detalles de las acciones cuando sea necesario **auditar o solucionar incidencias**.

{% hint style="danger" %}
El historial de los log se mantiene por dos meses en tu Fenicio. 
{% endhint %}


---

# 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://guia.fenicio.help/contenido-general/log-sistema.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.